![]() It seemed to be very slow going, and I suspect WiredTiger being acquired by 10gen had a part in it. There was work underway at the time I left to replace InnoDB with WiredTiger. Yeah, I used to work on DynamoDB, I know it's more complicated (much more complicated than that video makes out - their code quality was atrocious, like 2000-5000 line Java classes in 3 or 4 deep inheritance hierarchies no unit tests, only "smoke tests" that took 2 hours to run and were so prone to race conditions that common advice was to close everything else on your machine, run them, then leave them alone while you went to meetings) Perfect is the enemy of good enough, the architecture might be laughable to you, but it is probably miles ahead of what the customer was using before. It definitely sounds like it sucks from the perspective of an internal AWS developer or SRE, but if the AWS systems are architected such that these internal failures aren't seen by end users then AWS's reliability reputation remains fully intact.Ĭustomers are paying AWS so that their SREs don't get called, they don't care if the AWS SREs do as long as the system keeps running.īased on the supporting quotes at launch from Capital One, Dow Jones and WaPo it sound like enough customers are ok with vertical write scalability and (pretty awesome) horizontal read scalability for now because it fits their use case and is better than what they had before.Īlso consider that since the cluster management overhead has been removed from the customer, they can essentially "shard" by using a separate cluster for each sufficiently large service/org/dept, which might actually work out better for them in some respects.
0 Comments
Leave a Reply. |