120K distributed consistent writes per second with Calvin
1–10 of 73 posts
Re: 120K distributed consistent writes per second with Calvin
#2This is a new one to me...the referenced paper is here: http://cs.yale.edu/homes/thomson/publications/calvin-sigmod1...
How does this algorithm compare to whatever Google Spanner does?
Re: 120K distributed consistent writes per second with Calvin
#3This is a new one to me...the referenced paper is here: http://cs.yale.edu/homes/thomson/publications/calvin-sigmod1... How does this algorithm compare to whatever Google Spanner does?
That's a good and complicated question. They both are fully ACID-compliant systems. The biggest difference as a developer is that Calvin never blocks reads, contested or not. You get causally consistent single-replica reads with no coordination.
This makes the read performance equivalent to something like Cassandra at CONSISTENCY.ONE, without giving up the cross-partition write linearization of something like Spanner.
Re: 120K distributed consistent writes per second with Calvin
#4[deleted]
Re: 120K distributed consistent writes per second with Calvin
#5[deleted]
Re: 120K distributed consistent writes per second with Calvin
#6[deleted]
Re: 120K distributed consistent writes per second with Calvin
#7"Calvin's primary trade-off is that it doesn't support session transactions, so it's not well suited for SQL. Instead, transactions must be submitted atomically. Session transactions in SQL were designed for analytics, specifically human beings sitting at a workstation. They are pure overhead in a high-throughput operational context."
Is this specifically for distributed SQL only? I think there are some scalable SQL systems that don't support sessions either.
Re: 120K distributed consistent writes per second with Calvin
#8"Calvin's primary trade-off is that it doesn't support session transactions, so it's not well suited for SQL. Instead, transactions must be submitted atomically. Session transactions in SQL were designed for analytics, specifically human beings sitting at a workstation. They are pure overhead in a high-throughput operational context." Is this specifically for distributed SQL only? I think there are some scalable SQL…
Calvin is a generalized consistency protocol, that we use in FaunaDB to support relational semantics (but not SQL) in our database.
Multi-query transactions can be useful, but the FaunaDB query language is functional, rather than declarative like SQL, so composing queries that can do everything you want is usually easier than SQL.
Re: 120K distributed consistent writes per second with Calvin
#9"Calvin's primary trade-off is that it doesn't support session transactions, so it's not well suited for SQL. Instead, transactions must be submitted atomically. Session transactions in SQL were designed for analytics, specifically human beings sitting at a workstation. They are pure overhead in a high-throughput operational context." Is this specifically for distributed SQL only? I think there are some scalable SQL…
voltdb has no client-sessions though you have udf ones
Re: 120K distributed consistent writes per second with Calvin
#10This seems cool, and I sincerely wish them nothing but success. That said, I had a major sense of déjà vu while reading this post -- I worked at FoundationDB prior to the Apple acquisition, when we published a blog post with a very similar feel:
http://web.archive.org/web/20150325003241/http://blog.founda...
I'm not trying to make a comparison between a system I used to work on and one that I frankly know little to nothing about; rather, I'd suggest that building a system like this just isn't enough to be compelling on its own.