4 ms·
Was it considered to separate each table into its own S3 object?
by jsd1982 2y ago
Was it considered to separate each table into its own S3 object?
- jahewson 2y agoOnly if you don’t want transactions across tables?
- mbrt 2y agoIt's a good observation, because I did and decided to keep it out of scope from the base layer. But this is entirely possible. You can wrap GlassDB transactions and encode multiple keys into the same object at a higher level. Transactions across different objects will still preserve the same isolation. The current version is meant to be a base from which to build higer level APIs, somewhat like FoundationDB.