steepben

6 ms·

1.
Aurora DSQL: The Adjudicator(marc-bowes.com)
2 points by steepben 4mo ago|0 comments
2.
How DSQL makes sure sequences scale(blog.benjscho.dev)
11 points by steepben 8mo ago|1 comments
3.
by steepben 9mo ago
https://blog.benjscho.dev/
4.
by steepben 10mo ago
Ankush has moved on to Snowflake now, but he was previously at AWS.
5.
by steepben 2y ago
Yes it's a large chunk, but not everything! Marc had a comment on bluesky regarding this: > Many SQL aggregations are monotonic operations (e.g. MAX, SUM, etc) that can be partially completed on each node and then post-merged. Some
6.
by steepben 2y ago
There's a blog with more technical details: https://aws.amazon.com/blogs/database/introducing-amazon-aur... It provides strong consistency for cross-region transactions
7.
by steepben 2y ago
It's Postgres compatible, so not exactly non-portable
8.
by steepben 2y ago
There's a blog on the technical details here: https://aws.amazon.com/blogs/database/introducing-amazon-aur...
9.
by steepben 5y ago
According to page 128 of their S-1 filing [0], their claims bot "AI Jim" processes claims without human intervention in a third of cases, including automatically denying claims. So either the second tweet in the thread is a lie, o
10.
by steepben 6y ago
Nope! Actually going off better info now it looks like they WERE using rows, but it was in the old .xls format instead of .xlsx which limits to 2^16 rows https://twitter.com/standupmaths/status/1313149987707072512?
11.
by steepben 6y ago
Columns, they were using a column per case instead of a row per case.