PlanetScale & Vitess: Legacy Sharded Databases and Referential Integrity

1

Prisma GraphQL API

#Project Management #Workflow Automation #Web Service Automation 63 social mentions

2

PlanetScale

With all of this, you must be wondering: why would anybody want to use PlanetScale or Vitess? Well, I wonder the same. With many companies and websites, the reason was that they picked Vitess back when there weren't any better options. If you go to the beginning of the article, notice how it was created back in 2010. Now that we can enjoy an ACID-compliant scalable database with referential integrity, it would be in our best interest to shift towards these new databases, and I've started doing so already! Technology changes rapidly, and being up to date on.

#Vitess #Databases #Relational Databases 98 social mentions

3

Firebase

Let's briefly talk about what ACID Isolation is. There are four levels to it (according to the SQL-92 standards), including serialisability, read committed, read uncommitted, and repeatable reads. With that being said, there are more levels of isolation, such as Snapshot isolation which isn't a SQL standard although used by several databases such as Firebase or MongoDB. If you're further interested in this, I recommend reading this post. To keep it brief, I'm not going to go over what ever level of isolation does/means, but if you'd like to read more about that do check out this page from the MySQL Documentation.

#Developer Tools #App Development #Backend As A Service 246 social mentions

4

Google Cloud Spanner

This led me to be confused as to why they'd drop the FOREIGN KEY constraint as databases such as CockroachDB and Spanner still maintain referential integrity along with being scalable.

#Databases #Relational Databases #Tool 17 social mentions