pg_jsonschema
orioledb
pg_jsonschema | orioledb | |
---|---|---|
15 | 25 | |
929 | 2,640 | |
1.6% | 3.1% | |
6.6 | 9.2 | |
20 days ago | 3 days ago | |
Rust | C | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
pg_jsonschema
-
Introducing pgzx: create PostgreSQL extensions using Zig
And lots of interesting extensions use it, like
https://github.com/tembo-io/pgmq
https://github.com/zombodb/zombodb
https://github.com/supabase/pg_jsonschema
-
Beyond SQL: A relational database for modern applications
> In other words, there is still a (lossy) translation layer, it just happens to be in the RDBMS rather than in-app.
It's not lossy if your application can guarantee a json <-> datatype roundtrip and the json is validated with jsonschema (generated by your application)
In Rust it's something like this
https://serde.rs/ to do the data type <-> json mapping
https://docs.rs/schemars/latest/schemars/ to generate jsonschema from your types
https://github.com/supabase/pg_jsonschema to validate jsonschema in your database (postgres). with this setup it's interesting (but not required) to also use https://docs.rs/jsonschema/latest/jsonschema/ to validate the schema in your application
-
FerretDB, a truly open-source MongoDB alternative
Pretty exciting!
What about optionally validating some columns with jsonschema? Perhaps using https://github.com/supabase/pg_jsonschema - is using other postgres extensions supported in FerretDB? (if not, maybe it's feasible to incorporate the code of pg_jsonschema in FerretDB?)
- Type Constraints in 65 lines of SQL
-
Ask HN: Do you use JSON Schema? Help us shape its future stability guarantees
I'm not currently using it, but I'm strongly considering validating json in postgres with https://github.com/supabase/pg_jsonschema - which uses the https://docs.rs/jsonschema/latest/jsonschema/ Rust crate
So I'm not sure if my feedback is valid but, I sure hope that the jsonschema crate follows the spec! Otherwise I'll never use jsonschema but instead something-not-exactly-jsonschema. In other words.. you better not break anything.
-
Features I'd Like in PostgreSQL
Sounds dumb, but I want JSON field schema validation. I added a JSON column for flexible data, and although I'm happy with its flexibility, I kinda hope I can validate the JSON data structure. Recently I just found an extension [1] and will try soon.
[1] https://github.com/supabase/pg_jsonschema
-
Dynamic JSON schema validation, how can I do that in Postgres?
https://github.com/supabase/pg_jsonschema is new and looks good
-
Supabase Beta July 2022
Born as an excuse to play with pgx, pg_jsonschema is a solution we're exploring to allow enforcing more structure on json and jsonb typed postgres columns. Only 10 lines of code ๐
- GitHub - supabase/pg_jsonschema: PostgreSQL extension providing JSON Schema validation
- Show HN: Pg_jsonschema โ A Postgres extension for JSON validation
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
What are some alternatives?
windmill - Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool.
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
postgres-json-schema - JSON Schema validation for PostgreSQL
tsbs - Time Series Benchmark Suite, a tool for comparing and evaluating databases for time series data
pgx - Build Postgres Extensions with Rust! [Moved to: https://github.com/tcdi/pgrx]
timescale-analytics - Extension for more hyperfunctions, fully compatible with TimescaleDB and PostgreSQL ๐
is_jsonb_valid - Native PostgreSQL extension to validate jsonb
postgres - PostgreSQL with extensibility and performance patches
pg_ivm - IVM (Incremental View Maintenance) implementation as a PostgreSQL extension
plv8 - V8 Engine Javascript Procedural Language add-on for PostgreSQL
auth - A JWT based API for managing users and issuing JWT tokens
promscale - [DEPRECATED] Promscale is a unified metric and trace observability backend for Prometheus, Jaeger and OpenTelemetry built on PostgreSQL and TimescaleDB.