Always fun talking to developers about what databases they're using, what is/isn't working, and how we can solve real pain and help them move faster. Be sure to drop by the @fauna booth in the expo if you're at @AWSreInvent !
@eatonphil@sunbains They way I think about these 2PC systems is that they all use different ways to lower the cost of transaction ordering compared to 2PL. Percolator (and by extension TiDB) is unique here with the choice of a centralized oracle.
A thread about #NoSQL and serverside-functions.
The move from traditional #RDBMS to NoSQL #databases brought many advantages but also led to the loss of some critical features; one example is stored procedures. Cloud services like #AWS Lambda and #Azure Functions have attempted to fill this gap but often fall short in proximity to data, consistency, and regional constraints. @fauna's document-relational database model addresses these challenges by reintegrating stored procedure-like functionality directly within the database, negating the need for external services and their associated complexities for some use cases. It's not a replacement for all use cases!!!
There's an interesting disconnect between the religious fervor for SQL that has emerged over the last few years and the views of engineering leaders in my network that have experienced the pain of configuring/managing/scaling current SQL offerings, debugging complex/opaque performance issues stemming from ORM translation/query planner choices, etc. in the real world.
The SQL (re-)hype seems driven by the realization that relational features such as transactions, strong consistency, schema/enforcement, and first-class relationships are critical and are missing (or half-baked) in many NoSQL databases, which is very valid. But those features aren't intrinsically bound to SQL as a DQL/DML and they are front and center in modern NoSQL databases like @Fauna.
SQL was developed in the 1970s for humans writing analytical queries; it wasn't designed for operational databases that are primarily consumed by applications and the object–relational impedance mismatch is a real problem. The biggest benefit today is that it is a widely adopted standard, with many practitioners and a lot of tooling built around it. But languages and standards change over time, and the state of the art in operational databases has advanced to the point where that benefit typically isn't worth the cost.
Very excited about this! Lots of work by the team went into this launch. VPF gives you precise control over your Fauna deployment, including choice of cloud provider.
Today’s an exciting day for us at Fauna! 🎊 We’re thrilled to announce the launch of…
1️⃣ Intelligent Routing
2️⃣ Virtual Private Fauna
Both make it easier for developers to build performant and compliant apps with Fauna’s native serverless architecture…
snippet from our recent video with @fauna - why the future of serverless databases is distributed document-relational https://t.co/Cnf8lmmuLy. check out the whole conversation on youtube
Really excited streaming is out! Some powerful guarantees that didn't make it to the announcement post: Events are delivered in transaction order, and you can be guaranteed to never miss an event. Can't wait to see what folks build with this. https://t.co/vffJrCqt73
Sooo... I've always loved conlangs, but they're suuuuper difficult to model
So naturally I wrote this article in partnership with @fauna about how modelling conlangs gets much easier in NoSQL databases
https://t.co/eXJ7IuZqIE
Today, we're so excited to announce the Fauna + @vercel console-level integration. Now it's easier than ever to associate a Fauna database with your Vercel applications - try it out! https://t.co/VqrcvE2n20
#serverless#nextjs#fullstack#frontend