3 ms·
Somebody else asked this, but the answer got distracted onto (reasonably so) the CAP Theorem. What is the difference between Fauna and DynamoDB? Especially sin
by marknadal 10y ago
Somebody else asked this, but the answer got distracted onto (reasonably so) the CAP Theorem.
What is the difference between Fauna and DynamoDB? Especially since the article swaps them out (and explains the API differences).
DynamoDB is going to be having a replica you can read from within physical milliseconds of your lambda function (serverless is such a bad name, makes me think of P2P, anyways...) while it seems like Fauna is gonna have to make network calls out to your service...
Which when you pay per time with lambda, and you want lambda functions to be fast anyways, I don't see the point of Fauna? Note: I'm not saying Fauna is bad, it seems like a cool idea, but I'm not understanding how it is a superior alternative.
So lets say you don't want to pay for DynamoDB, it still seems like you'd be better off running something like a pure NodeJS database like Parse's open source server or https://github.com/amark/gun https://github.com/amark/gun , either inside the lambda function directly or connecting to it (since it'll be on a nearby machine in AWS)?
- evanweaver 10y agoFaunaDB is hosted in several AWS regions around the world, so the latency is similar to DynamoDB if you're colocated. We will expand to more AWS regions and other cloud providers soon. The biggest operational difference between FaunaDB and DynamoDB, aside from being globally distributed, is that you don't have to pre-provision capacity in FaunaDB. DynamoDB requires you to provision capacity per table and you have to pay for whatever you don't use. If you go over the provisioned capacity your app stops working. FaunaDB is delivered like a utility; you just pay as you go. Also FaunaDB supports joins, transactions, unique indexes, views, etc., and you can install it on-premises if you want.
- marknadal 10y agoThanks for the answer!