5 ms·
This article seems to uncritically assume that microservices are a good idea. If you want to microserviceize a legacy app, go ahead, but I doubt that using cont
by wmf 10y ago
This article seems to uncritically assume that microservices are a good idea. If you want to microserviceize a legacy app, go ahead, but I doubt that using containers is a good excuse to do so.
Also, it seems to me that containers would be perfect for code written in weird no-longer-supported languages since you could presumably containerize the compiler without having to fight with incompatibilities caused by newer distros.
- benjaminwootton 10y agoThanks for that and good feedback. I also wrote this a while back so I'm definetly aware of the challenges of Microservice based apps - http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html http://highscalability.com/blog/2014/4/8/microservices-not-a...
- drieddust 10y agoAn honest question, I am just beginning to understand containers so it might be naive. Containers share kernel from the base operating system so when kernel updates to new incompatible version with breaking changes, how containerize application will continue to work.
- pgeorgi 10y agoThe kernel interface tends to be super stable (eg on Linux, kernel interface ABI breakage is a blocker bug, and Linus rants about that every now and then when people ignore this). So it shouldn't be too painful to run RedHat 4.1 (from 1997) in a container on top of current Linux 4.8 and use that to run software linked against that ancient set of libraries. Probably easier than getting all those libraries to run in a current era userland.
- drieddust 10y agoThanks understood, that means forward compatibility is guaranteed mostly.
- user5994461 10y agoDid you try that? I am experiencing so many issues with Docker and current kernels. I can only envision an attempt to run RedHat 4.1 over a modern system as a recipe for disaster.
- drieddust 10y agoWhat kind of issues you have got into? I would like to hear from you. Though I don't have any experience of managing containers, argument does not make a lot of sense to me. They are pitched as holy grail which will get rid of entire IT team managing the operating system i.e. upgrades, patching, and configuration management. It just looks counter-intuitive to me as any new upgrade, bug fix , or security patch still needs to be applied to base OS. Containerized application can move freely from one host OS to another host OS but they will still depend on same underlying environment.
- jacques_chester 10y ago> They are pitched as holy grail which will get rid of entire IT team managing the operating system i.e. upgrades, patching, and configuration management. They don't. Containers push a lot of that responsibility out to the developers. You still need operators if you're running your own IaaS substrate. Disclosure: I work for Pivotal, we do some stuff with containers.
- deleted 10y ago[deleted]
- user5994461 10y ago> What kind of issues you have got into? I would like to hear from you. See my blog post here. https://thehftguy.wordpress.com/2016/11/01/docker-in-production-an-history-of-failure/ https://thehftguy.wordpress.com/2016/11/01/docker-in-product...
- jacques_chester 10y ago