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.

All of which end up getting allocated to a single 56 core cpu.

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. :)

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.

It still shows up in 2000 lines of stack traces when an exception occurs. For comparison a similar stack traces in Asp.net Core is 20 lines...