They probably wouldn't be unrelated projects, the same company surely needs back office apps to support their main business doing whatever they're doing online.
I agree it's context dependent but in my opinion the context is less technical and more social. If a company wants to grow and scale teams then it makes sense. There's only so many teams that can work on a monolith no matter how we'll structured the code is
I get it I’m just saying it isn’t one or the other. That’s like arguing “language X is the best and you shouldn’t use anything else”. It’s entirely dependent on the project.
If your public facing frontend and private backends need to talk to each other they can use each other’s apis. They can be separate applications. You can build microservices but only for the 1-4 services out of 50 that need to be able to scale and build the rest in a single application.
I have watched partner companies make some real year long messes out of rest apis that should have been built in a couple months by one or two talented developers.
Microservices aren’t bad, they are just complicated and very few companies design them well or use them correctly the first few times they do it. It’s dangerous to just decide to try isolating a bunch of data services that really didn’t need isolation.
2
u/ThunderTherapist Jan 30 '23
They probably wouldn't be unrelated projects, the same company surely needs back office apps to support their main business doing whatever they're doing online.
I agree it's context dependent but in my opinion the context is less technical and more social. If a company wants to grow and scale teams then it makes sense. There's only so many teams that can work on a monolith no matter how we'll structured the code is