3 ms·
You are setting up an entire operating system to install a single Microservice and just now noticed that you have redundancies? You could have the same issue b
by choeger 8y ago
You are setting up an entire operating system to install a single Microservice and just now noticed that you have redundancies?
You could have the same issue by simply trying to rpmbuild your app. No really, you are just doing packaging. If you want more comfort, look into how redhat or Debian maintain their packages. They have similar problems and most likely they have mature solutions.
- viraptor 8y agoIf you have a single service and will never want more - sure. Once you have multiple, you actually get benefits if you depend on a lot of native libraries and external binaries. If you're in that situation, not having to upgrade every service at the same time when moving to a new base os release is really convenient.
- Apaec 8y agoNixOS offers the same benefits(more actually). Without containers.
- corndoge 8y agoWhy learn how to do it right when you can just ship a filesystem in a box instead? sbuild manpage is too long!
- 420codebro 8y agoI'm confused - what is the alternative you are advocating? Said micro-service is coded in X, requiring Y libraries, etc. Docker satisfies packaging all of that together, removing host-OS dependency hell (who the fuck wants to go back to that stupid shit?)