Why Build Your Own?
Look, I know what you're thinking. "Why not just use Elasticsearch?" or "What about Algolia?" Those are valid options, but they come with complexity. You need to learn their APIs, manage their infrastructure, and deal with their quirks.
Sometimes you just want something that:
Works with your existing database
Doesn't require external services
Is easy to understand and debug
Actually finds relevant results
That's what I built. A search engine that uses your existing database, respects your current architecture, and gives you full control over how it works.
The Core Idea
The concept is simple: tokenize everything, store it, then match tokens when searching.
... continue reading