Re:Not microservice or monolith; it's cognitive load you nee...
by philote on Saturday December 30, 2023 @08:12AM
(#38815026)
I think the confusion is because "something new" isn't necessarily a completely new, disconnected product. It could be something like adding multi-lingual support to an existing product. In that case, you often do need to coordinate across many teams to get the new feature implemented, which can be a huge pain in a micro-service architecture.
Re:Not microservice or monolith; it's cognitive load you nee...
by randomdata on Sunday December 31, 2023 @12:34PM
(#38825775)
No more than it is a pain in a service architecture – being the exactly same thing, just in a different economy. As always, if a service doesn't do what you need, you build your own in-house. Just because there is a product on the market is that is kind of, sort of, but not really, what you need doesn't mean you must use it.
You don’t try to build something new with 10,000 developers, if that’s where you have become confused.