While this is a true horror story, this is how I feel about microservices. Simple things take forever because the unnecessary complexity is through the roof. I do not experience the "developer ergonomics" that I used to.
Every microservice will get its own share or lack thereof of love, have possibly different wiring, be written in a different language, and may or may not have good enough tests. Most likely the system integration tests are non-existent either so good luck with that regression.
That's after you figure out how to set up your environment locally just for this one task, making sure that all services are up to date, starting properly, have the right local settings, and communicate with each other without issues.
> Most likely the system integration tests are non-existent either so good luck with that regression.
I remember once taking down production by adding some health checks to a microservice that someone had thrown over the fence. Of course there were no integration tests, but this microservice wasn't deployed in staging environments either, so production was the only place to test it.
I once brought down a major financial services application (in production, because of course) by adding _logging_ to a certain tight loop. The assignment was to log every iteration of that loop. Worst job of my life.
In the beginning of my career I worked on a volatile multidimensional house of cards project. It was a classic ASP enterprise content management system, patched together by external contractors for 10 years or so, with seemingly no structure at all. The code base was truly “magical” in the sense that it was a miracle that it sort of worked. Contained a number of “don’t change this” and gotchas.
Projects like this doesn’t build character, it just sucks.
Parts of this feel very familiar to me - years ago I worked on a PHP application originally built in 2003 and it was a jenga tower of missing closing tags in included files that somehow worked, but couldn't be changed because of all the different places they were included.
Me too. One place I worked, the CTO called their (medical) software a dried up pile of *stuff. Every time you would scratch the surface it would just flake off and fall apart in your hand.
Every microservice will get its own share or lack thereof of love, have possibly different wiring, be written in a different language, and may or may not have good enough tests. Most likely the system integration tests are non-existent either so good luck with that regression.
That's after you figure out how to set up your environment locally just for this one task, making sure that all services are up to date, starting properly, have the right local settings, and communicate with each other without issues.
What should take minutes now takes days.