News for hackers. Stuff that matters.
Re:Amazon DynamoDB Transactions by ryanworl on Tuesday November 27, 2018 @07:38PM (#18548263)
“DynamoDB is the only non-relational database that supports transactions across multiple partitions and tables.”

Uh... this is just not true.

Re:Amazon DynamoDB Transactions by otterley on Tuesday November 27, 2018 @09:29PM (#18548787)
Can you identify some others?
Re:Amazon DynamoDB Transactions by stickfigure on Tuesday November 27, 2018 @10:18PM (#18549029)
The Google Cloud Datastore (formerly the "App Engine Datastore") has had cross-entity-group transactions since 2011:

https://googleappengine.blogspot.com/2011/10/app-engine-155-...

Re:Amazon DynamoDB Transactions by airwot4 on Wednesday November 28, 2018 @05:38AM (#18550540)
The cross group transactions are a little limited - https://cloud.google.com/appengine/docs/standard/java/datast...

I don't think it's fair to compare them.

However, the more recent Google storage offerings based on Cloud Spanner do seem to offer this. I don't see how Amazon can make this statement - that doesn't stop it being an excellent enhancement to DynamoDB though.

Re:Amazon DynamoDB Transactions by wsh91 on Wednesday November 28, 2018 @04:06PM (#18555698)
Cloud Firestore (the next generation of Cloud Datastore) removes those limitations. https://cloud.google.com/firestore/docs/manage-data/transact...

It also supports the Cloud Datastore API.

(I work on it!)

Re:Amazon DynamoDB Transactions by itcmcgrath on Thursday November 29, 2018 @02:18PM (#18562992)
DynamoDB is limited to 10 items, whereas the Cloud Datastore limits are 25 different 'tables' -> The new version via Cloud Firestore doesn't even have that restriction. AWS is several years behind and several NoSQL systems behind in this area. Still, a cool addition.
Re:Amazon DynamoDB Transactions by kevan on Wednesday November 28, 2018 @10:25AM (#18552241)
I don't know if the overall statement is true, but Spanner is relational and the statement was limited to non-relational databases.
Re:Amazon DynamoDB Transactions by otterley on Wednesday November 28, 2018 @03:52AM (#18550154)
The “and tables” clause is the differentiator, I think. DynamoDB tables are roughly equivalent to Datastore namespaces; I don’t believe Google Cloud Datastore supports cross-namespace transactions.
Re:Amazon DynamoDB Transactions by itcmcgrath on Thursday November 29, 2018 @02:18PM (#18563001)
It does, and has for several years.
Re:Amazon DynamoDB Transactions by monstrado on Tuesday November 27, 2018 @09:47PM (#18548878)
FoundationDB https://www.foundationdb.org/ not only supports transactions, they are mandatory. They also go one step further and support atomic operations, which are especially killer.
Re:Amazon DynamoDB Transactions by otterley on Wednesday November 28, 2018 @03:57AM (#18550164)
I don’t think FDB supports cross-database transactions, though.
Re:Amazon DynamoDB Transactions by ryanworl on Wednesday November 28, 2018 @05:23AM (#18550486)
What do you mean by this? There is only one “database” in FoundationDB terms. You can write transactions over the entire keyspace regardless of which machine the data is stored on.
Re:Amazon DynamoDB Transactions by otterley on Wednesday November 28, 2018 @10:47AM (#18552415)
Multiple clusters, then, or whatever you specify to FDB’s API to identify the instance when making a client connection.
Re:Amazon DynamoDB Transactions by ryanworl on Wednesday November 28, 2018 @11:12AM (#18552648)
I'm still not sure what you mean in terms of contrasting this with DynamoDB's new features. You could implement the entire DynamoDB API, with even stronger semantics than the new features listed in the article, on top of FoundationDB. Additionally, the latency would be theoretically lower as they describe needing to do a read, write, and another read per key to verify isolation, whereas FoundationDB uses an optimistic concurrency control scheme to verify at commit time that transactions do not conflict. In the common case (where transactions don't conflict) this is faster.
Re:Amazon DynamoDB Transactions by otterley on Wednesday November 28, 2018 @11:23AM (#18552765)
All I’m trying to do here is trying to see whether the claim made in the blog post is true or not. Some commenters were claiming it was false, but I don’t think they considered all the components of the claim.
Re:Amazon DynamoDB Transactions by monstrado on Wednesday November 28, 2018 @11:33AM (#18552892)
Agreed 100% and as someone who has had to use DDB before, nothing would make me happier than seeing this built.
Re:Amazon DynamoDB Transactions by monstrado on Wednesday November 28, 2018 @09:22AM (#18551619)
There's not really a concept of "Database" in FDB. There is however a concept of key spaces, and "directories", which are basically the same, and these all support transactions.

i.e.

/database1/key1 = foo

/database2/key2 = bar

Re:Amazon DynamoDB Transactions by airwot4 on Wednesday November 28, 2018 @05:31AM (#18550517)
As far as I'm aware these offerings support transactions across the entire database.

Google Cloud Spanner: https://cloud.google.com/spanner/docs/transactions

Google Cloud Firestore: https://firebase.google.com/docs/firestore/manage-data/trans...

Plus if you use Cloud Firestore in Datastore Mode then Google Cloud Datastore would satisfy this requirement as well.

Re:Amazon DynamoDB Transactions by otterley on Wednesday November 28, 2018 @11:07AM (#18552588)
Spanner is not a non-relational database.

As for Firestore, it’s not clear whether it supports cross-collection transactions. Cloud Datastore does not support cross-namespace transactions AFAICT.

Re:Amazon DynamoDB Transactions by wsh91 on Wednesday November 28, 2018 @04:09PM (#18555726)
a) Cloud Firestore supports transactions across the entire database. You can learn more about them here: https://cloud.google.com/firestore/docs/manage-data/transact....

b) Given that the primary use case for namespaces was/is multitenancy, it's not clear to me why you'd want to transact across them. Nevertheless, you can. What's leading you to draw this conclusion?

Re:Amazon DynamoDB Transactions by otterley on Wednesday November 28, 2018 @04:23PM (#18555809)
The documentation is what led me to that conclusion, since it's not explicit as to what the transaction boundaries are, but I could be mistaken. Does this mean that the poster's claim is erroneous?
Re:Amazon DynamoDB Transactions by itcmcgrath on Thursday November 29, 2018 @02:19PM (#18563015)
It does. It's not in the documentation because it doesn't have boundaries within the database.
Re:Amazon DynamoDB Transactions by otterley on Thursday November 29, 2018 @04:55PM (#18564472)
Can you have more than one database per project? If so, there still might be a valid claim here.
Re:Amazon DynamoDB Transactions by gmaster1440 on Tuesday November 27, 2018 @10:25PM (#18549067)
MongoDB (https://www.mongodb.com/transactions)

“Multi-document transactions can be used across multiple operations, collections, databases, and documents.”

Re:Amazon DynamoDB Transactions by otterley on Wednesday November 28, 2018 @03:54AM (#18550159)
However: “Multi-document transactions are available for replica sets only. Transactions for sharded clusters are scheduled for MongoDB 4.2.” DynamoDB is sharded by design.
Re:Amazon DynamoDB Transactions by gmaster1440 on Wednesday November 28, 2018 @01:48PM (#18554375)
I see, it appears to come down to how each db interprets "partitions".

If we're referring specifically to shards then "DynamoDB is the only non-relational database that supports transactions across multiple partitions and tables." no longer sounds like hyperbole.

Re:Amazon DynamoDB Transactions by AaronFriel on Wednesday November 28, 2018 @01:20AM (#18549642)
Hyperdex Warp - I'm not sure if it's still available - which purports to provide serializability over multi-key transactions. In the HyperDex model that means over all defined spaces in the cluster. That's a stronger guarantee than DynamoDB provides, which is still susceptible to phantom reads. The DynamoDB team ought to be aware of it, because it's one of the first hits for "multi-key transactions" and the paper is an important one for designing transactions on KVS.

https://arxiv.org/pdf/1509.07815.pdf

Re:Amazon DynamoDB Transactions by winetraveler on Wednesday November 28, 2018 @12:10PM (#18553276)
FaunaDB (mentioned in previous comment) -- it is multi-model NoSQL so you can do relational queries and it supports transactions across multiple partitions, documents, replicas. json docs, not tables.
Re:Amazon DynamoDB Transactions by Nican on Wednesday November 28, 2018 @04:23PM (#18555811)
CockroachDB And you can get pretty close to being schemlass with the json column, and maybe with the inverted index.
Re:Amazon DynamoDB Transactions by philliphaydon on Wednesday November 28, 2018 @04:04AM (#18550198)
RavenDB I think?