4 ms·
After X11 and Spring, the Maximum Abstraction Task Force shifted to focus on infrastructure, which is why your Java Virtual Machine processes are now running as
by inopinatus 7y ago
After X11 and Spring, the Maximum Abstraction Task Force shifted to focus on infrastructure, which is why your Java Virtual Machine processes are now running as a uniquely allocated user ID in a container scheduled by a control plane on a pool of OS instances separated by the hypervisor service of a dynamically sized cloud placement group.
- infogulch 7y agoAll of which end up getting allocated to a single 56 core cpu.
- keanebean86 7y agoEven the CPU adds at least one layer of abstraction. Spring JVM Container OS hypervisor x86 Real CPU instructions Electrons Unknown EDIT: formatting
- dmitriid 7y agoAnd "EDIT: formatting" is now an additional layer, too :)
- majewsky 7y agoThat's the layer that's argued about the most. :)
- inopinatus 7y agoThis process is called “Devops”
- gruez 7y agoAre hypervisors and containers really abstractions though? All they do is manage access to the underlying resource.
- catern 7y agoA hypervisor definitely is; the "hardware" interface for a kernel running as a (performant) VM is different from the hardware interface for real hardware. I think one could argue that containers aren't much of an abstraction for the running program itself, though, as you say. The place where containers provide an abstraction is at deployment time/process management time; the program itself has (essentially) the same API whether it's running in a container or not.