2 ms·
In my experience, engineers will be pushing for microservices as often if not more than tech management. The reasons are sometimes different - a lot of times it
by ryanbrunner 6y ago
In my experience, engineers will be pushing for microservices as often if not more than tech management. The reasons are sometimes different - a lot of times it reduces down to "our existing services are all written with old, unsexy technology and I want to do something greenfields with new tech that looks good on my resume", but they're definitely not fighting against the tide of management insisting on microservices.
- sdevonoes 6y agoI see that as well, but only if microservices have been already "approved" in your organization (usually by upper tech management).
- devonkim 6y agoAnother reason I’ve seen is “this project will be around for a while and we should skip past the growing pains to go into microservices.” If it’s a rewrite of an existing system, then it’s more justifiable because it’s about eliminating technical debt and is not a greenfield project. But for new efforts where an organization has never seen customer demand in X, Y, Z services being created it’s pure conjecture and premature optimization to essential refactor across service boundaries before a monolith with some usage metrics even exists