Congratulations! and some sympathies re: Java/gradle/maven
Containerization's one of those things that I've got badly mixed feelings on. Too many businesses (and open source communities!) use it as an alternative to actually understanding and managing their dependency graph or actually setting up sane requirements. But the whole 'full isolation and discrete permissions' is good! But it's trivially easy to set up a container that doesn't actually live up to that. Most of big formats have surprisingly good behavior. But the performance overhead for using networking for every form of interprocess communication can get pricey, and even if you don't care about performance the implementation and documentation is near-universally pants.
But if you need to be able to take a server functionality out behind the shed and Ol' Yeller it, it's hard to beat, and much more practical for that purpose than having twenty VMs rolling around.
p
Congratulations! and some sympathies re: Java/gradle/maven
Containerization's one of those things that I've got badly mixed feelings on. Too many businesses (and open source communities!) use it as an alternative to actually understanding and managing their dependency graph or actually setting up sane requirements. But the whole 'full isolation and discrete permissions' is good! But it's trivially easy to set up a container that doesn't actually live up to that. Most of big formats have surprisingly good behavior. But the performance overhead for using networking for every form of interprocess communication can get pricey, and even if you don't care about performance the implementation and documentation is near-universally pants.
But if you need to be able to take a server functionality out behind the shed and Ol' Yeller it, it's hard to beat, and much more practical for that purpose than having twenty VMs rolling around.
More options
Context Copy link