4 ms·
>> If you have a monorepo, good build tooling, and a good infrastructure as code tool, Yep, and so many organisations ignore these. Especially after a less suc
by cgrealy 6y ago
>> If you have a monorepo, good build tooling, and a good infrastructure as code tool,
Yep, and so many organisations ignore these. Especially after a less successful transition to micro-services.
"you mean you want to spend more time doing non-customer visible development? You just did that micro services thing a while ago!"
"Yes, but to take proper advantage of that we need to invest in the right infrastructure and tooling"
"how can I sell that?"
- throwaway894345 6y agoHonestly, that sounds like the devops team didn't communicate well with the business when they pitched them microservices. The business can't reasonably know that moving to microservices entails a change in infrastructure and tooling--you have to build that into your high level estimates.
- cgrealy 6y agoOften, they didn’t. How many stories have we all heard about “wow.. transitioning to microservices was way harder than we expected” followed by a move back to monolith instead of fixing the issues. That doesn’t mean a micro service architecture is wrong... just that you have to either learn from your mistakes or hire an amazingly talented team... that have learned from mistakes somewhere else.