orioledb
MeiliSearch
Our great sponsors
orioledb | MeiliSearch | |
---|---|---|
25 | 129 | |
2,631 | 43,397 | |
3.6% | 3.4% | |
9.3 | 9.8 | |
14 days ago | 4 days ago | |
C | Rust | |
GNU General Public License v3.0 or later | MIT License |
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.
orioledb
-
Supabase Acquires OrioleDB
hey hn, supabase ceo here
we've been fans of Oriole for a while now and have been long-time supporters
in case you're jumping straight to the comments: OrioleDB is a table storage extension for Postgres. it acts as a drop-in replacement for the default postgres storage engine using the Table Access Method APIs (pluggable storage). the storage engine changes the representation of table data on disk. its architecture is designed to take advantage of modern hardware like SSDs and NVRAM. it implements MVCC, the feature that allows allows multiple connected users to see different versions of the data depending on when their transaction started, via an UNDO log rather than tuple versioning.
one caveat: it requires several patches to the postgres core to expand on the type of features external storage engines extensions can implement. for this reason it could be a while before you see this land as a default engine on supabase. we will probably make it available as an option for customers who want to experiment - no timeline is decided yet.
finally, we have been working with the team on decoupled storage and compute [0]. this is experimental but promising, especially with some recent advances in S3 (specifically Express One Zone [1]). we have a demonstration in the blog post.
i'll message Alexander in case there are any technical questions
[0] https://github.com/orioledb/orioledb/blob/main/doc/usage.md#...
[1] https://aws.amazon.com/s3/storage-classes/express-one-zone/
-
Jepsen: MySQL 8.0.34
When I saw "cloud native" I was expecting S3-ish the way Neon does it but they say it's experimental: https://github.com/orioledb/orioledb/blob/beta4/doc/usage.md... and for them to say "beta, don't use in production" and then a separate "experimental" label must make it really bad
-
When Did Postgres Become Cool?
There are some interesting things in development to potentially solve that problem.
Here's a recent HN submission about OrioleDB of the more promising ones: https://news.ycombinator.com/item?id=36740921
Source code: https://github.com/orioledb/orioledb
-
PostgreSQL: No More Vacuum, No More Bloat
https://github.com/orioledb/orioledb/blob/main/doc/arch.md
> - PostgreSQL is very conservative (maybe extremely) conservative about data safety (mostly achieved via fsync-ing at the right times), and that propagates through the IO stack, including SSD firmware, to cause slowdowns
This is why our first goal is to become pure extension. Becoming part of PostgreSQL would require test of time.
> - MVCC is very nice for concurrent access - the Oriole doc doesn't say with what concurrency are the graphs achieved
Good catch. I've added information about VM type and concurrency to the blog post.
> - The title of the Oriole doc and its intro text center about solving VACUUM, which is of course a good goal, but I don't think they show that the "square wave" graphs they achieve for PostgreSQL are really in majority caused by VACUUM. Other benchmarks, like Percona's (https://www.percona.com/blog/evaluating-checkpointing-in-pos...) don't yield this very distinctive square wave pattern.
Yes, it's true. The square patters is because of checkpointing. The reason of improvements here is actually not VACUUM, but modification of relevant indexes only (and row-level WAL, which decreases overall IO).
- OrioleDB Reached Beta
- OrioleDB β building a modern cloud-native storage engine for Postgres
-
The Part of PostgreSQL We Hate the Most (Multi-Version Concurrency Control)
I took a look at https://github.com/orioledb/orioledb which is a project attempting to remedy some of Postgres' shortcomings, including MVCC. It looks like they're doing something similar to MySQL with a redo log, as well as some other optimizations. So maybe this is the answer.
-
Production grade databases in Rust
You donβt need a database written (or rewritten in Rust). weβre working to make Postgres scalable for the next decade too https://github.com/orioledb/orioledb
-
Features I'd Like in PostgreSQL
> Iβd love to see B-Tree primary storage option. Aka store the row data inside the primary index.
It is coming: https://github.com/orioledb/orioledb
-
Supabase-JS v2
sorry to underwhelm!
if you like Neon, then I imagine you like their database branching model? On Friday we announced[0] our 500K investment into OrioleDB, who are working on branching[1], with the plan to upstream these changes into Postgres core.
It would be possible for us to run a fork of Postgres today which supports branching, but our long-term view is that developers would prefer a non-forked version of Postgre (to mitigate any risk of lock-in). So we will work on adding branching to Postgres core in the background, which will be a benefit to the entire Postgres ecosystem.
[0] Announcement:https://supabase.com/blog/supabase-series-b#where-were-going
[1] https://github.com/orioledb/orioledb/wiki/Database-branching
MeiliSearch
-
Publish/Subscribe with Sidekiq
We needed to introduce a new service for search. As we settled on using meilisearch, we needed a way to sync updates on our models with the records in meilisearch. We could've continued to use callbacks but we needed something better.
-
The Mechanics of Silicon Valley Pump and Dump Schemes
Meilisearch
-
What is Hybrid Search?
In this case, a good strategy is to use vector search only when the keyword/prefix search returns none or just a small number of results. A good candidate for this is MeiliSearch. It uses custom ranking rules to provide results as fast as the user can type.
-
Create a ChatBot with VertexAI and LibreChat
With the VertexAI endpoint set up and tested, our next step is to work with LibreChat. LibreChat is an open-source ChatGPT clone that can integrate with various AI models, including the PaLM 2 models via the VertexAI API. It's built using React, MongoDB, and Meilisearch technologies.
-
Pg_bm25: Elastic-Quality Full Text Search Inside Postgres
Meilisearch seems like it is the best open source option.
https://www.meilisearch.com/
- Looking for an easy installable search engine for a shared hosting account? Any ideas?
- Meilisearch: Build an intuitive search experience in a snap
-
Vector storage is coming to Meilisearch to empower search through AI
Starting with v1.3, you can use Meilisearch as a vector store. Meilisearch allows you to store vector embeddings alongside your documents conveniently. You will need to create the vector embeddings using your third-party tool of choice (Hugging Face, OpenAI). As we published the first v1.3 release candidate, you can try out vector search today.
-
[N] Open-source search engine Meilisearch launches vector search
I work at Meilisearch, an open-source search engine built in Rust. π¦
-
Creating search engine for your local network - Is it even possible?
https://www.meilisearch.com/ https://github.com/meilisearch
What are some alternatives?
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
Typesense - Open Source alternative to Algolia + Pinecone and an Easier-to-Use alternative to ElasticSearch β‘ π β¨ Fast, typo tolerant, in-memory fuzzy Search Engine for building delightful search experiences
tsbs - Time Series Benchmark Suite, a tool for comparing and evaluating databases for time series data
zincsearch - ZincSearch . A lightweight alternative to elasticsearch that requires minimal resources, written in Go.
timescale-analytics - Extension for more hyperfunctions, fully compatible with TimescaleDB and PostgreSQL π
Elasticsearch - Free and Open, Distributed, RESTful Search Engine
postgres - PostgreSQL with extensibility and performance patches
Searx - Privacy-respecting metasearch engine
plv8 - V8 Engine Javascript Procedural Language add-on for PostgreSQL
sonic - π¦ Fast, lightweight & schema-less search backend. An alternative to Elasticsearch that runs on a few MBs of RAM.
promscale - [DEPRECATED] Promscale is a unified metric and trace observability backend for Prometheus, Jaeger and OpenTelemetry built on PostgreSQL and TimescaleDB.
rust-postgres - Native PostgreSQL driver for the Rust programming language