4 ms·
Fair enough. However, my opinion of this matter still stands. I think something like a library or even an executable/process should try to decouple itself from
by ziikutv 10y ago
Fair enough. However, my opinion of this matter still stands. I think something like a library or even an executable/process should try to decouple itself from deployment process; and should be designed as such. Its very opinionated - I must admit - but it tends to take away a lot of friction from adopting. Also, usually, when we add things like Docker to the mix, it is quiet unclear if the said microservice can function without Docker (perhaps it's using something X specific and cannot work without it); if it can, lets mention it otherwise even if it is something I want, I won't spend the time to test it myself (yeah I am very a very picky lad I know but I bet this is something a lot of people do)
- computerex 10y agoWhat are you talking about. Docker is a tool that positively contributes to the deployment experience and reduces friction in adoption. It is one of the tools that directly contributed to the adoption of microservices because it makes dealing with a large number of services (500+) sane and possible. You should learn more about docker and dev-ops, because with microservices the focus is increasingly towards having developers support their services end-to-end, which means the devs are responsible for deploying/supporting the services they wrote in production.
- collyw 10y ago>Docker is a tool that positively contributes to the deployment experience and reduces friction in adoption. Well its one more things to install for starters. Do I need a specific version of docker to run with this? To me it's just an extra layer of complexity.