Hacker News Reader

Comment by toomuchtodo | Hacker News Reader

To your point, Shopify's monolith was handling 1.27M requests/sec on Black Friday: https://twitter.com/ShopifyEng/status/1597983918900510720

Thread: https://threadreaderapp.com/thread/1597983918900510720.html

View on HN

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.

> 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)

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

Way way way more of our code in Ruby.

Go (and now Rust) is really only used for very low level services with a high SLA (Like Infrastructure). Almost all business logic is Ruby + Rails.

True but you’re still putting significant investment into ruby to speed it up. Ruby is slow.

I don’t think any other company could do that.

Reply on news.ycombinator.com