News for hackers. Stuff that matters.
Re:Building Domain Driven Microservices by sandGorgon on Tuesday July 07, 2020 @05:03AM (#23757118)
you can do islands of communications in a monolith as well, with the added advantage of significantly lower deployment complexity as well lower incidental complexity
Re:Building Domain Driven Microservices by collyw on Tuesday July 07, 2020 @09:50AM (#23759234)
I view a working microservices application as a monolith with unreliable network connections between components. So overall adding a lot more complexity for the promise of lowers costs and scale-ability.

One advantage that I do see is the ability to deploy components individually, but I see more downsides than benefits overall. I hope that consensus is becoming "start with a (modular, well designed) monolith and scale out the parts as needed".

Re:Building Domain Driven Microservices by tluyben2 on Tuesday July 07, 2020 @05:14AM (#23757179)
And (much) lower deployment costs, lower staffing costs, and lower development costs... In my experience anyway.
Re:Building Domain Driven Microservices by pragmaticdev on Tuesday July 07, 2020 @07:45AM (#23758169)
This is only true for trivially small products. The pipeline complexity for multi-team monoliths can consume an entire dev team to maintain.