orama VS sonic

Orama, an open-source, edge-first hybrid search engine highlights the industry's shift towards more efficient, accurate, and scalable solutions. Recent trends indicate a shift from traditional search solutions to more modern and efficient answering engines like Orama, evidenced by the search features on both Node.js and SolidJS that were formerly powered by Algolia, but are now powered by Orama.

Let's break into the steps to utilize Orama and analyze how it works. I won't dig into the technical stuff because, hey, it's an open-source project, which means you can easily peek at the source code, no problemo!

If you are interested in it, you can learn more about it in the official documentation. And don't forget to follow Orama on Twitter and Michere Riva its CTO.

I'll use the Lyra repository for this article, so thanks to the Lyra contributors if this article has a great git history and awesome code.

You can checkout lyra, its in-memory full text search engine for javascript

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