Re:The Cracking Monolith: Forces That Call for Microservices
by witheld123 on Wednesday March 22, 2017 @07:05AM
(#13929954)
Isn't it hard to maintain all the servers? How do you upgrade your application or your database?
[ Parent
| on HN ]
Re:The Cracking Monolith: Forces That Call for Microservices
by icebraining on Wednesday March 22, 2017 @07:20AM
(#13930021)
We automate it :) There's an "inventory" of the current instances, and then using configuration management (currently Ansible) we can deploy a new version (running migrations, starting new processes and stop old ones, etc) for all or any subset of our instances with a single command.
Re:The Cracking Monolith: Forces That Call for Microservices
by barrkel on Wednesday March 22, 2017 @07:16AM
(#13930007)
This is why you use configuration management tools. We have a similar architecture, with dozens of deployments for customers; upgrades are just a single command that changes some configuration, and puppet does the rest. Until something goes wrong, 100 servers are no harder to upgrade than 1.
Re:The Cracking Monolith: Forces That Call for Microservices
by al2o3cr on Wednesday March 22, 2017 @08:57AM
(#13930488)
It does sound like upgrading all the customer servers would be a hassle, but that might be a feature in some domains - if customers have process / regulatory / training constraints and don't want to upgrade promptly, for instance.