3 ms·
Without regard to the merit of each tech, I've made the J2EE to K8S comparison before and am glad to see here I am not the only one who saw the resemblance. It
by speed_spread 6y ago
Without regard to the merit of each tech, I've made the J2EE to K8S comparison before and am glad to see here I am not the only one who saw the resemblance.
It mostly goes to show that containerizing application code for execution in a managed environment in nothing new. I'm sure this was also done somehow in the mainframe world.
As to whether K8S is a superior embodiment of the concept, I'd say that the problem is rather that a large majority of adopters are just cargo-culting without having a real need for what it actually provides, externalizing the costs of complexity it brings. I have nothing against K8S itself, but its adoption curve is telling of CV-driven architecture at it's worst. Mind you, the same might have been said of J2EE back in the day.
- pcdavid 6y ago> It mostly goes to show that containerizing application code for execution in a managed environment in nothing new. I'm sure this was also done somehow in the mainframe world. Yes, it's called an operating system :-)
- gjvc 6y ago> I'm sure this was also done somehow in the mainframe world. LPAR -- https://en.wikipedia.org/wiki/Logical_partition https://en.wikipedia.org/wiki/Logical_partition Upon understanding this, I realised that there is / was nothing new under the sun.
- pjmlp 6y agoEven safe systems programming languages, with unsafe code blocks. https://en.wikipedia.org/wiki/Burroughs_large_systems https://en.wikipedia.org/wiki/Burroughs_large_systems https://en.wikipedia.org/wiki/NEWP https://en.wikipedia.org/wiki/NEWP If you follow NEWP manual from Unisys (nowadays still selling Burroughs as ClearPath), you will see UNSAFE code blocks and how its use tainted binaries, which requires admin permission for execution.