Re:Write Libraries, Not Frameworks
by inopinatus on Friday May 08, 2020 @11:54PM
(#23122162)
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.
[ Parent
| on HN ]
All of which end up getting allocated to a single 56 core cpu.
Re:Write Libraries, Not Frameworks
by keanebean86 on Saturday May 09, 2020 @02:39AM
(#23122779)
Even the CPU adds at least one layer of abstraction.
Spring
JVM
Container
OS
hypervisor
x86
Real CPU instructions
Electrons
Unknown
EDIT: formatting
And "EDIT: formatting" is now an additional layer, too :)
That's the layer that's argued about the most. :)
Re:Write Libraries, Not Frameworks
by inopinatus on Saturday May 09, 2020 @07:05PM
(#23128965)
This process is called “Devops”
Are hypervisors and containers really abstractions though? All they do is manage access to the underlying resource.
A 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.