proleisuretour

Totally agree with the puzzling assortment of a rubric. PostgreSQL supports role based-access control, RBAC. Not to mention, with PostgreSQL and the pgvector extension, you have a whole list of languages ready to use it:

C++ pgvector-cpp C# pgvector-dotnet Crystal pgvector-crystal Dart pgvector-dart Elixir pgvector-elixir Go pgvector-go Haskell pgvector-haskell Java, Scala pgvector-java Julia pgvector-julia Lua pgvector-lua Node.js pgvector-node Perl pgvector-perl PHP pgvector-php Python pgvector-python R pgvector-r Ruby pgvector-ruby, Neighbor Rust pgvector-rust Swift pgvector-swift

Wonder how many of those other Vector databases play nice.

Definitely agree with Branson's top 10 of challenges with PostgreSQL, especially #3: "Inefficient Replication That Spreads Corruption". Postgres WAL entries are always the bottleneck of a replication stream.

There's a big difference between wire and syntax compatibility. This compatibility matrix does a nice job of showing the differences between vendors. But yeah, purpose-built databases have a place.

Most folks can't even access the article because it a pay wall. So by design, the pay wall creates avoidance.

This is a great article about building global apps that require multi-region deployments. Thanks for sharing. Curious about the transaction retry errors for UPDATE that required 2 days to resolve. Probably could of been avoided using a distributed SQL database that supports a read committed isolation level ¯\_(ツ)_/¯ For those going down this path, maybe check out open source YugabyteDB. There is a great doc about how to build Global Apps using various application design patterns: https://docs.yugabyte.com/preview/develop/build-global-apps/

Man, I miss those tape drives and a good game of Snake!

yeah... no burgers or tacos https://www.theverge.com/2023/6/13/23759857/amazon-aws-down-...

that's WHY you need at least a multi-region HA database for your apps

not good lol

pretty interesting ... covers replication strategies and tools, read replicas, coordinators, sharding, and the new tech stack approach... job well done