Postgres's dominance is well deserved, of course. My only concerns with it, both are actively worked on, are bloat management (significant for update heavy workloads and programmers used to the MySQL model of rollback segments) and the scaling of concurrency (going over 500 connections). Bloat was taken over by Cybertec[1] after stalling for a bit and is funded (yay), while concurrency was also enhanced out of Micros…
Another concern, no temporal tables, don't businesses demand this feature?
Databases in 2021: A Year in Review
51–60 of 136 posts
Re: Databases in 2021: A Year in Review
#52Wow I kind of feel like I'm reading about Javascript frameworks. I don't recognize any of the dbs or companies/projects. Didn't realize the db world was so busy
Re: Databases in 2021: A Year in Review
#53Re: Databases in 2021: A Year in Review
#54Earlier quoted context omitted.
Cloud SQL data warehouses like Snowflake and BigQuery.
I just wish AWS had something as good as BigQuery.
Re: Databases in 2021: A Year in Review
#55I expected more mentions of Vitess, which honestly looks like some kind of alien black magic from what I saw while consulting for a client this year. But I guess not much else happened to it other than PlanetScale.
Which part most impressed you and which part seems like magic? Their devs / contributors are active on here...
--------
An architect demoed the failure of a shard and the automatic promotion of its backup shard to main, in production. They actually test their failure models.As I see it, sharding is not very hard. HA is not very hard given a reasonable SLA. But sharding with HA on a large setup that actually works is pretty hard.
Another thing that stuck in my mind was their high throughput-per-provisioned-hardware ratio. With not much hardware they were pulling 80k queries per second with room to spare.
Although I have to say, that's not much compared to GitHub which pulls 1.2 million queries/sec on Vitess [0].
[0] https://github.blog/2021-09-27-partitioning-githubs-relation...
Re: Databases in 2021: A Year in Review
#56Excited to see Dgraph on the top 10 mentions and climbing above neo4j
Re: Databases in 2021: A Year in Review
#57Postgres's dominance is well deserved, of course. My only concerns with it, both are actively worked on, are bloat management (significant for update heavy workloads and programmers used to the MySQL model of rollback segments) and the scaling of concurrency (going over 500 connections). Bloat was taken over by Cybertec[1] after stalling for a bit and is funded (yay), while concurrency was also enhanced out of Micros…
Re: Databases in 2021: A Year in Review
#58So a company that sells PostgreSQL services thinks PostgreSQL is dominating. Brilliant. The reality is that nothing is dominating. In 2021 there were more databases than ever each addressing a different use case. Companies don't have just one EDW they will have dozens even hundreds of siloed data stores. Startups will start with one for everything, then split out auth, user analytics, telemetry etc There is no eviden…
Couple of points: 1. Ottertune doesn't sell PostgreSQL services, they sell a database optimization service that happens to support PostgreSQL (and other databases like MySQL) 2. PostgreSQL is definitely gaining market shares and fast, see the db-engine graph [1], you can compare it to the oracle trend if you are not convinced [2] [1] https://db-engines.com/en/ranking_trend/system/PostgreSQL [2] https://db-engines.com…
Re: Databases in 2021: A Year in Review
#59Wow I kind of feel like I'm reading about Javascript frameworks. I don't recognize any of the dbs or companies/projects. Didn't realize the db world was so busy
Not even PostgreSQL?
Re: Databases in 2021: A Year in Review
#60My DB discovery and the game changer of 2021 was EdgeDB.