Is running a separate instance of the monolith with a separate database for every store really "a monolith" withstanding 1.27M rps?
It's a bit like saying Magento served 1M rps on Black Friday leaving out the small but important detail that each individual store has separate infrastructure and manageable load.
Divide and conquer works, congrats to the Shopify team that their design decisions worked out for their use case. And obviously some parts of the system are still shared but my guess is that they are not part of the monolith.
Re:McDonalds Event Driven Architecture
by tiffanyh on Tuesday December 06, 2022 @08:23PM
(#33889575)
> averaging 3 Terabytes per minute of egress traffic across our infrastructure. That’s 4.3 Petabytes per day!
I’d hate to get that AWS bandwidth bill.
On the other hand, 4.3 Petabytes of VISA/MasterCard traffic is a bill you'd probably be happy to pay. (It's Shopify after all, not Flickr)
Re:McDonalds Event Driven Architecture
by spoils19 on Tuesday December 06, 2022 @10:11PM
(#33890210)
Exactly. I've written and maintained monoliths that handle close to ~20M requests per second, and it only went down once (when somebody tripped over the power cable!)
But ruby is too slow!
Lots of their code is in Go
Thread: https://threadreaderapp.com/thread/1597983918900510720.html