Earlier quoted context omitted.
"Probably async"? Could you expand on it?
To achieve "availability", cassandra lowers consistency, making dev's life extremely hard. Long: https://docs.yugabyte.com/latest/comparisons/cassandra/ TLDR: google/fb/etc went the other way, using hbase,bigtable witch are strongly consistent.
FoundationDB Record Layer
81–85 of 85 posts
Re: FoundationDB Record Layer
#82Earlier quoted context omitted.
To achieve "availability", cassandra lowers consistency, making dev's life extremely hard. Long: https://docs.yugabyte.com/latest/comparisons/cassandra/ TLDR: google/fb/etc went the other way, using hbase,bigtable witch are strongly consistent.
Cassandra has monotonic reads so it is strongly consistent as long as you have a quorum of nodes. I haven't yet read the link you posted but it's coming from a vendor that is aiming to replace Cassandra so I'll take it a pinch of salt.
Re: FoundationDB Record Layer
#83Re: FoundationDB Record Layer
#84Earlier quoted context omitted.
Cassandra has monotonic reads so it is strongly consistent as long as you have a quorum of nodes. I haven't yet read the link you posted but it's coming from a vendor that is aiming to replace Cassandra so I'll take it a pinch of salt.
No salt required. You can replace it with any strongly consistent system that has transactions and it's the same.
Re: FoundationDB Record Layer
#85Earlier quoted context omitted.
No salt required. You can replace it with any strongly consistent system that has transactions and it's the same.
I see. Has Amazon replaced Dynamo with Postgres? Has Google replaced BigTable with MySQL?