A lead architect wants to break a stable monolith into 47 microservices — even though the app only handles about 2 requests per second. A reddit post from r/softwarearchitecture that perfectly captures the ongoing debate between developers and architects about when to split a monolith. Is it really about scaling? Or something else entirely?
🔗 Kurrent (formely EventStoreDB)
https://kurrent.io
🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1
💥 Join this channel to get access to a private Discord Server and any source code in my videos.
🔥 Join via Patreon
https://www.patreon.com/codeopinion
✔️ Join via YouTube
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join
📝 Blog: https://codeopinion.com
👋 Twitter: https://twitter.com/codeopinion
✨ LinkedIn: https://www.linkedin.com/in/dcomartin/
📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeopinion
0:00 Requests per Second
2:30 Perspective
3:20 Organizational Scale
5:39 Scaling a Monolith
6:39 Value
Original post: https://www.reddit.com/r/softwarearchitecture/comments/1o6re10/lead_architect_wants_to_break_our_monolith_into/
