3 ms·
Our org made all the right decisions at the top, invented their own microservice fabric stuff with way too much tech debt, end result was a very bad (inefficien
by dionian 9y ago
Our org made all the right decisions at the top, invented their own microservice fabric stuff with way too much tech debt, end result was a very bad (inefficient and painful) development experience with way more technical debt than the monolith we replaced.
There was so much fragmentation between each autonomous team that we were forced to standardize on a common framework (think of build/integration pipelines and common modules) which could almost never be changed or refactored.
The upside was that there was way more automated testing and flexibility in deployment, so overall it was a net gain.
Still, the actual ergonomics of working with the build/release system was so painful it made me leave to work somewhere where I could do actual innovation.
There was so much waste that was already 'baked into the system' and the other teams finished their work so if you had struggles with it it was your problem
- mattmanser 9y agoOverall a net gain, but it made you leave? That definitely does not sound like an overall net gain.
- dionian 9y agoIt was a net gain for them.. They were doing even worse before. They upgraded to a CD style pipeline to AWS instead of monolithic java apps. It was better but nobody realized there were deep and very wrong tech debt. The complacency around this was a big factor in causing me to seek new challenges. The biggest pain points were always not the OSS stuff that was adopted, it was all the “NIH” innovations that were developed because the OSS stuff wasn’t quite right, stuff that “worked” but had no support or allowances for improvement.
- deleted 9y ago[deleted]