51–52 of 52 posts
Amazingly little to no use of images in the articles. Turning the 'an image is worth a thousand words' on its head. Seems to work well though. Examples: https://aws.amazon.com/builders-library/avoiding-insurmounta... , https://aws.amazon.com/builders-library/caching-challenges-a...
Earlier quoted context omitted.
Yes, that's a great one. But now I have a brain teaser stuck in my head: Imagine you have a multi-tenant system like they describe, but for each customer A, B, C they have users A1, A2, A3, B1 etc. You need ordered delivery of messages, but only at user level (if all messages needed to be ordered you could not do this sharding type setup). Is there a way to apply shuffle sharding while maintaining user-level ordering…
Yes! we do recursive, nested, shuffle sharding in these cases. Our Open Source infima library doesn't quite include direct support for this, but you can get a sense of how we put it all together: https://github.com/awslabs/route53-infima