r7n

5 ms·

1. 1.▲
   by r7n 3mo ago

   We obsessed over optimizations and pushing the apis to the limits of how we could pack it. So much so, we re-wrote the DynamoSDK to squeeze out more optimizations so we could be the same cost even though we were a layer in front of dynamo.
2. 2.▲
   by r7n 3mo ago

   Agreed, my critique was about how the article frames scalability. I've yet to see an OLTP problem that can't live in something like Dynamo. KV can model anything if you put in the work, the question is how much modeling discipline
3. 3.▲
   by r7n 3mo ago

   I've extensively used Dynamo (internally at Amazon and externally) and even founded a DB startup with it at it's core. Boiling down scalability of Postgres vs Dynamo as it's written in blog is a bit terse. Dynamo scales write
4. 4.▲
   by r7n 1y ago

   We did exactly this when designing StatleyDB. We realized there are a set of metadata fields[0] that almost everyone needs when modeling data. Our approach takes this a step further in that we always track these fields transparently so if y