sonic VS opensearch

Sonic - a project written in Rust, uses custom network communication protocol for fast communication between the client and the server.

This is uncanny, I just discovered ArchiveBox earlier today and set up a self-hosted instance on some home hardware for a collection of bookmarks of useful guides, tutorials, and references I've collected over the years.

Setting it up on K8s with sonic [1] as the search backend and importing a few hundred URLs only took ~an hour or so, and the cached pages look great for the most part.

[1] https://github.com/valeriansaliou/sonic

If you don't need advanced search features, you can use Sonic (https://github.com/valeriansaliou/sonic). It's blazing fast and you can save lot of money on servers.

What about Sonic? Maybe it requires a bit of integration, but it's simple and blazing fast.

git clone https://github.com/valeriansaliou/sonic.git

- Sonic (https://github.com/valeriansaliou/sonic)

There isn't enough out there comparing all these for the simple typical fuzzy search/search box usecase -- which I think is 80% of people doing search today.

Like other people are pointing out, most of these engines won't have all the features of ES (or more accurately Lucene) but I am pretty convinced that most of the time it doesn't actually matter and if someone is searching on your site excessively maybe there's a problem with your UX (unless you're a search engine or repository of information).

[0]: https://supabase.com/blog/postgres-full-text-search-vs-the-r...

Or just right-click the input field, and if the browser recognizes it as a search field (they're good at it by default, but you can implement https://github.com/dewitt/opensearch to make extra sure), you'll get an option to create a search from it, with a keyword of your choosing (haven't tried Safari).

https://github.com/public-apis/public-apis https://data.gov.sg/developer http://opendatacommunities.org/ https://www.data.gov/developers/apis https://data.sfgov.org/browse?limitTo=datasets&utf8=? https://mashupaustralia.org/open-access-to-psi/ https://catalogue.data.govt.nz/dataset https://rapidapi.com/ https://www.programmableweb.com/apis https://rapidapi.com/collection/list-of-free-apis https://any-api.com/ https://compassioninpolitics.wordpress.com/2009/06/03/best-free-apis-for-web-developers/ https://rapidapi.com/pozzad/api/email-validator-1 https://public-apis.xyz/ https://developers.facebook.com/ https://dev.twitter.com https://www.programmableweb.com/news/5-weather-apis-weatherbug-to-weather-channel/2009/04/15 https://duckduckgo.com/api https://openweathermap.org/api https://github.com/dewitt/opensearch http://www.atomenabled.org/ https://openid.net/developers/ http://developer.foodessentials.com/ https://postcoder.com/docs/address-lookup https://github.com/public-apis/public-apis https://www.data.gov/developers/apis https://rapidapi.com/ https://www.programmableweb.com/apis https://rapidapi.com/collection/list-of-free-apis https://any-api.com/ https://compassioninpolitics.wordpress.com/2009/06/03/best-free-apis-for-web-developers/ https://rapidapi.com/pozzad/api/email-validator-1 https://public-apis.xyz/ https://www.programmableweb.com/news/5-weather-apis-weatherbug-to-weather-channel/2009/04/15 https://duckduckgo.com/api https://openweathermap.org/api https://postcoder.com/docs/address-lookup https://postcoder.com/docs/address-lookup http://vendapin.com/cecb46.html https://my-json-server.typicode.com/ https://jsonplaceholder.typicode.com/ https://reqres.in/ https://my-json-server.typicode.com/ https://randomapi.com/pricing https://randomuser.me/ https://reqres.in/ https://randomapi.com/pricing http://www.mindit-bookmarking.com/ https://theroadtodelphi.com/2010/08/07/using-the-google-maps-api-v3-from-delphi-part-i-basic-functionality/ https://theroadtodelphi.com/2010/08/07/using-the-google-maps-api-v3-from-delphi-part-i-basic-functionality/ https://www.geoapify.com/map-marker-icons-generator-create-beautiful-icons-for-your-map https://elevation-api.io/ https://open-elevation.com/ https://www.thoughtco.com/save-a-web-page-as-html-or-mht-1058361 https://theroadtodelphi.com/2010/08/07/using-the-google-maps-api-v3-from-delphi-part-i-basic-functionality/ https://www.programmableweb.com/apis/directory https://www.sitepoint.com/10-html5-apis-worth-looking/ http://www.99lime.com/elements/ https://docs.angularjs.org/api https://docs.angularjs.org/api/ng/service/$http https://docs.angularjs.org/api/ngMock/service/$httpBackend https://developers.google.com/earth/ http://www.worldwindcentral.com/wiki/Google_Earth_comparison https://theroadtodelphi.com/2010/08/07/using-the-google-maps-api-v3-from-delphi-part-i-basic-functionality/ https://jasontpenny.com/blog/2009/01/11/google-maps-in-a-twebbrowser-from-delphi-directions/ https://geochalkboard.wordpress.com/2009/03/11/density-mapping-in-google-maps-with-heatmapapi/ https://www.ixxat.com/products/products-industrial/protocol-sw-and-apis https://docs.microsoft.com/en-us/dotnet/api/system.componentmodel.backgroundworker?redirectedfrom=MSDN&view=netframework-4.7.2 http://custforum.axis.com/viewtopic.php?t=1963&sid=7990ea009d57544606efd627f3a40541 https://stackoverflow.com/questions/5137717/seeking-simple-coding-example-for-axis-webcam-using-vapix

I still quite like the idea of having a number of independent search engines each indexing their own specialist subjects, and one or more federated search front-ends which can pull these together.

Doing it with APIs is a little tricky to make work in a usable way though. There have been various attempts at standardised APIs, e.g. OpenSearch[0], and metasearch engines like searX[1] have what are essentially pluggable scrapers, but there are still fundamental issues like getting different results at different times and having different ranking mechanisms.

Integrating at the index level could make a more usable search, but there are lots of other issues with this approach, e.g. those with Apache Solr's Cross Data Centre Replication[2]. And yes, the volumes of data may also be an issue, given a search index will typically be slightly larger than the compressed data size, e.g. the 16M wikipedia docs are approx 32Gb compressed and approx 40.75Gb in a search index.

[0] https://github.com/dewitt/opensearch , unrelated to Amazon's Elasticsearch fork

[1] https://github.com/searx/searx

[2] https://solr.apache.org/guide/8_11/cross-data-center-replica...

GitHub

OpenSearch was once was an initiative founded at A9, Amazon subsidiary, to create a personalized, cross-service, search engine: https://archive.is/PCKWq

OpenSearch is from an era when Amazon and Google were covertly competitive. Google didn't get anywhere with Froogle and AppEngine; whilst Alexa and A9 didn't move any mountains.

Code: https://github.com/dewitt/opensearch