Title is very misleading and seems like a quickly written article. How 30TB handling is possible using modular monolith but not in microservice based design? Where it went wrong?
Totally agree with Nabil, the title is a clickbait and irrelevant with the content. I would like to know what difficulties Shopify meet with this traffic size under this code arch and what solutions Shopify come up with.
Modular monolith has nothing to do with traffic. They have to handle traffic by aggressive caching on the server side. Modular monolith is about maintainability and extensibility.
Title is very misleading and seems like a quickly written article. How 30TB handling is possible using modular monolith but not in microservice based design? Where it went wrong?
I see, thanks for the feedback.
The idea was to give an introduction to the modular monolith with this case study.
Totally agree with Nabil, the title is a clickbait and irrelevant with the content. I would like to know what difficulties Shopify meet with this traffic size under this code arch and what solutions Shopify come up with.
This is all just too abstract to me. Can you show us how exactly to implement it? Maybe share a github repo?
Modular monolith has nothing to do with traffic. They have to handle traffic by aggressive caching on the server side. Modular monolith is about maintainability and extensibility.