orioledb
postgrest-js
orioledb | postgrest-js | |
---|---|---|
25 | 12 | |
2,685 | 945 | |
2.0% | 1.9% | |
9.2 | 7.5 | |
11 days ago | 4 days ago | |
C | TypeScript | |
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
postgrest-js
-
Ask HN: What are some unpopular technologies you wish people knew more about?
At one point, I really thought it was used in Supabase. But I guess they only wrote the js wrapper for it. https://github.com/supabase/postgrest-js
Came here to mention Hasura as well (not sure of it's popularity though) https://hasura.io/graphql/database/postgresql
-
Why supabase client don't introduce min, max and count functions
Min/Max looks like it still has to be done via RPC (with sample code here) https://github.com/supabase/postgrest-js/issues/206
- Completely baffled about async call.
-
Why to use Supabase instead of Prisma (or any other ORM) with a Postgres DB?
There's nothing wrong with this and they're pretty open about it. But the SDK they provide for direct database operations is the weakest of the ones I've used, when it should be the strongest I think. It leverages PostgREST which is a tool for auto generating REST APIs from schemas. From the README: "The goal of this library is to make an "ORM-like" restful interface."
-
Should I use Prisma to get data or Supabase itself to get data
Looks like there's an open github issue that might answer some of your questions: https://github.com/supabase/postgrest-js/issues/303
-
Supabase secrets management available in beta
I think it’s great too. I wish they would shore up some of their existing releases though. Probably most notably, the ability to query aggregates via the officially supported route is missing: https://github.com/supabase/postgrest-js/issues/206
The workarounds suggested are not ergonomic for most use cases and it feels pretty out of place for such basic functionality to be missing in what otherwise feels like a pretty full featured product.
Their Realtime product is another example of something that languishes while new features get launched.
-
Need help looking for a tool
I haven't completely understood what you are looking for but I think Supabase could be potential useful alternative backend for you supabase.io ?
-
How I Built Skillbit: Linktree, but for Your Skills
I used postgrest-js to communicate with my PostgREST endpoint. The library is easy to use and does everything for you.
-
Supabase-JS v2
yes you're right. The JS library is a thin wrapper around PostgREST's API (https://github.com/supabase/postgrest-js)
Supabase now offers a few more features which integrate with the Postgres database - File Storage (s3), Authentication, Deno Functions, and Realtime (database change listeners). Each of these services is a standalone server and each has a corresponding JS library.
"supabase-js" wraps up the modular JS libraries into a single library for convenience
-
Supabase May 21: Apple and Twitter Logins, Supabase Grid, Go and Swift Libraries
* Swift Libraries are now underway thanks to @satishbabariya [2]
We still have a long way to go for mobile support, but the Apple logins is a big one. If you ship an app to the App Store with any third-party logins, you're required to enable Apple logins as well. While this sounds like a bit of over-reach, it's actually quite cool - if you use Apple login they obfuscate your email so that the 3rd party app don't get access to your personal data. Quite nice!
[0] CSV: https://github.com/supabase/postgrest-js/pull/187
What are some alternatives?
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
nuxt3-supabase - Nuxt 3 module and composables for Supabase.
tsbs - Time Series Benchmark Suite, a tool for comparing and evaluating databases for time series data
solid-supabase - A simple wrapper around Supabase.js to enable usage within Solid.
timescale-analytics - Extension for more hyperfunctions, fully compatible with TimescaleDB and PostgreSQL 📈
gotrue-swift - A Swift client library for GoTrue.
postgres - PostgreSQL with extensibility and performance patches
postgrest-go - Isomorphic Go client for PostgREST. (Now Updating)
plv8 - V8 Engine Javascript Procedural Language add-on for PostgreSQL
vue-supabase - A supa simple wrapper around Supabase.js to enable usage within Vue.
promscale - [DEPRECATED] Promscale is a unified metric and trace observability backend for Prometheus, Jaeger and OpenTelemetry built on PostgreSQL and TimescaleDB.
flarebase-auth - Firebase/Admin Auth Javascript Library for Cloudflare Workers