Timeline for answer to Managing Growth in Microservice Architecture: Is Modular Monolith the Solution? by nicholaswmin

Current License: CC BY-SA 4.0

Post Revisions

8 events

when toggle format	what		by	license	comment
Aug 1, 2025 at 10:29	history	edited	nicholaswmin	CC BY-SA 4.0	added 185 characters in body
Jul 29, 2025 at 14:48	comment	added	nicholaswmin		You have too many systems around you but at the same time you have a team with finite patience and a brain with finite capacity. Low coupling isn't a standalone saying, it's full-form is "low coupling, high cohesion"; there's a reason for that. So you're gonna have to actually do the engineering part where you make a personal, reasoned, executive decision and say regardless of the clamoring of this authority guy, and this other book, my situation requires X/Y/Z and this is what's gonna happen - slowly and steadily. Don't panic and dump it all for the extreme opposite.
Jul 29, 2025 at 10:18	comment	added	User1254		Marking as solved due to the typically useful material provided about microservices and their patterns. Thank you. :)
Jul 29, 2025 at 10:17	vote	accept	User1254
Jul 28, 2025 at 10:49	comment	added	User1254		The problem is that we have too many systems around us, all wanting to integrate with each other, and we end up acting as a proxy. I know tools like IBM API Connect can help with this, but until now, we've been handling it through separate microservices. Yes, you're right, we could establish some boundaries. That's what I'm trying to do right now. I'm thinking of consolidating for example five microservices under a specific sub-domain into one, instead of maintaining multiple separate ones.
Jul 25, 2025 at 22:55	history	edited	nicholaswmin	CC BY-SA 4.0	added 84 characters in body
Jul 25, 2025 at 22:43	history	edited	nicholaswmin	CC BY-SA 4.0	added 84 characters in body
Jul 25, 2025 at 22:38	history	answered	nicholaswmin	CC BY-SA 4.0