bayard
Typesense
bayard | Typesense | |
---|---|---|
4 | 131 | |
1,839 | 18,107 | |
0.0% | 3.4% | |
0.0 | 9.8 | |
about 1 year ago | 3 days ago | |
Rust | C++ | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bayard
-
An alternative to Elasticsearch that runs on a few MBs of RAM
Somewhat related, this guy: https://github.com/mosuka/ seems to be very passionate about search service.
He built two distributed search services:
- https://github.com/mosuka/phalanx, written in Go.
- https://github.com/mosuka/bayard, written in Rust.
-
Postgres Full Text Search vs. the Rest
I wish we had an extension like ZomboDB but using a lighter search engine like https://github.com/quickwit-oss/quickwit, https://github.com/toshi-search/Toshi and https://github.com/mosuka/bayard
Here I'm listing engines based on https://github.com/quickwit-oss/tantivy - tantivy is comparable to Lucene in its scope - but I'm sure there are other engines that could tackle ElasticSearch.
Another thing that could happen is maybe directly embed tantivy in Postgres using an extension, perhaps this could be an option too.
-
Meilisearch, the Rust search engine, just raised $5M
So there's more than one? The one I knew was https://github.com/quickwit-oss/tantivy and https://github.com/quickwit-oss/quickwit on top of it (there's a couple of other search engines built on top of tantivy, like https://github.com/bayard-search/bayard)
Typesense
-
FlowDiver: The Road to SSR - Part 1
Disregarding props-drilling technique in favor of a more reliable and elegant solution we looked for inspiration elsewhere. Another project of ours .find was using Typesense/Algolia components, which looked a bit like black-box/magic, but at the same time provided a clean approach to build complex and highly customizable solutions.
-
Release Radar · April 2024 Edition: Major updates from the open source community
Have you ever tried to look up something, only to realise your search engine doesn't recognise your typos? Typesense to the rescue! It's a fast, typo-tolerant search engine built for an easier browsing experience. The latest version comes with new features such as built-in conversational search, image search, voice search, analytics, and more. Dive into the release notes for the full list of changes and enhancements.
-
Website Search Hurts My Feelings
There are actually plenty of non-ES products that are way easier to integrate and tune (and get better results with less effort).
- Typesense (https://github.com/typesense/typesense)
- Algolia
- Google Programmable Search Engine (https://programmablesearchengine.google.com/about/)
- Remote Machine Learning and Searching on a Raspberry Pi 5
-
Open Source alternatives to tools you Pay for
Typesense - Open Source Alternative to Algolia
-
DNS record "hn.algolia.com" is gone
If you like your penny take a look at Typesense https://typesense.org/ - nothing to complain here. Especially nothing complain about pricing.
-
Vector databases: analyzing the trade-offs
I work on Typesense [1] (historically considered an open source alternative to Algolia).
We then launched vector search in Jan 2023, and just last week we launched the ability to generate embeddings from within Typesense.
You'd just need to send JSON data, and Typesense can generate embeddings for your data using OpenAI, PaLM API, or built-in models like S-BERT, E-5, etc (running on a GPU if you prefer) [2]
You can then do a hybrid (keyword + semantic) search by just sending the search keywords to Typesense, and Typesense will automatically generate embeddings for you internally and return a ranked list of keyword results weaved with semantic results (using Rank Fusion).
You can also combine filtering, faceting, typo tolerance, etc - the things Typesense already had.
[1] https://github.com/typesense/typesense
[2] https://typesense.org/docs/0.25.0/api/vector-search.html
-
Creating an advanced search engine with PostgreSQL
For something small with a minimal footprint, I'd recommend Typesense. https://github.com/typesense/typesense
-
Obsidian Publish full text search
I haven’t used Publish, but I’d assume you could use something like https://typesense.org/ to index and search the vault.
-
DynamoDB search options
A cheaper option would be to use https://typesense.org. You can use DynamoDb streams to automatically load records. It has worked well for me.
What are some alternatives?
quickwit - Cloud-native search engine for observability. An open-source alternative to Datadog, Elasticsearch, Loki, and Tempo.
MeiliSearch - A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
tantivy - Tantivy is a full-text search engine library inspired by Apache Lucene and written in Rust
Elasticsearch - Free and Open, Distributed, RESTful Search Engine
sonic - 🦔 Fast, lightweight & schema-less search backend. An alternative to Elasticsearch that runs on a few MBs of RAM.
Apache Solr - Apache Lucene and Solr open-source search software
zincsearch - ZincSearch . A lightweight alternative to elasticsearch that requires minimal resources, written in Go.
meilisearch-laravel-scout - MeiliSearch integration for Laravel Scout
quickwit - Quickwit is a fast and cost-efficient distributed search engine for large-scale, immutable data. [Moved to: https://github.com/quickwit-oss/quickwit]
loki - Like Prometheus, but for logs.
lyra - 🌌 Fast, in-memory, typo-tolerant, full-text search engine written in TypeScript. [Moved to: https://github.com/LyraSearch/lyra]