News for hackers. Stuff that matters.
Re:Don't start with microservices – monoliths are your friend by outworlder on Thursday December 16, 2021 @02:48PM (#29582940)
> Micro services were not an answer to monolith being bad

Micro services today are mostly used for one purpose: to be able to ship your corporation's org chart.

Re:Don't start with microservices – monoliths are your friend by mbrodersen on Friday December 17, 2021 @07:08PM (#29599917)
Not really. You could do the same by having different organisational units being responsible for different libraries. And the final monolith being minimum glue code combined with N libraries. Basically the same way your code depend on libraries from other vendors/OSS maintainers.
Re:Don't start with microservices – monoliths are your friend by one2three4 on Thursday December 16, 2021 @04:24PM (#29584117)
You do that anyway as per Conway's law.
Re:Don't start with microservices – monoliths are your friend by actually_a_dog on Thursday December 16, 2021 @03:42PM (#29583620)
> Micro services today are mostly used for one purpose: to be able to ship your corporation's org chart.

And, this is not necessarily a bad thing.

Re:Don't start with microservices – monoliths are your friend by danjac on Friday December 17, 2021 @04:24AM (#29589817)
The problem is that orgs are not set in stone. Teams get merged and split in reorgs, buyouts and mergers happen, suddenly your microservices designed around "cleanly defined boundaries" no longer make any sense. Sure you can write completely new microservices but that is a distraction from delivering value to the end customer.
Re:Don't start with microservices – monoliths are your friend by actually_a_dog on Saturday December 18, 2021 @04:06AM (#29603030)
So? The solution is that services travel with teams. I've been through more than one reorg. That's what always happens. The point is to have clear ownership and prevent conflicts from too many people working on the same code.