2/7: Abstraction & Sediment Taming The Stack

 | 
20.08.2026
 | 
2 min read
Featured Image

The global digital supply mesh gives organizations access to technologies and investments they could never reproduce themselves. But it also creates a practical problem: no engineer and no organization can understand the billions of technological connections underneath the services they use. Two mechanisms make this complexity manageable: abstraction and sediment.

Abstraction: How Engineers Tame the Mesh

Abstraction is an old engineering principle. When we flip a light switch, we do not need to understand the power plant, electricity grid and wiring behind it. We only need to understand the interface: the switch.

Software works the same way. Engineers use databases without understanding how every byte is stored, deploy applications to clouds without knowing the physical machines underneath, and call AI models without understanding the infrastructure and software required to operate them. Computing has continuously added such layers: databases hid storage complexity behind SQL, virtualization hid physical hardware, cloud computing hid data centers behind APIs, and AI increasingly hides complex computation behind natural language interfaces.

This is what makes the Mesh usable. Abstraction does not remove complexity. It allows us to use complexity without understanding it.

Sediment: Technology Rarely Leaves

At the same time, organizations rarely replace an entire technological generation when the next one arrives. A working mainframe was not removed when client server computing arrived. Those systems remained when the web appeared, just as web applications remained when organizations adopted cloud computing.

Replacing working systems is expensive and risky, so the rational choice is usually to connect rather than replace: build an interface, expose an API, add middleware or wrap the existing system. Over decades, mainframes, client server applications, web systems, cloud services and now AI therefore accumulate inside the same organization.

This accumulated technological history is technology sediment.

Nobody designs this sediment as a whole. It emerges from thousands of individually rational decisions made by different people at different times. Applications become connected to databases, infrastructure, tools, business processes and people until replacing one component means untangling everything that has grown around it. Many of those connections may no longer be fully documented or even known.

Digital opportunities & risks share the same origin

Abstraction allows organizations to use complexity without understanding it. Sediment allows them to adopt new technology without rebuilding what already works. Together, they make the global digital supply mesh economically manageable, but they also create opacity and dependencies that can be extremely difficult to remove.

And this is where digital sovereignty enters the picture: the mechanisms that create the Mesh's enormous value are also the mechanisms that create its risks. But what exactly are those risks, and what value do we get in return? See the next chapter.

All text, data and graphics...

...the blog posts and background information may be used according to the license terms, including for commercial purposes. They are available as open files under ‘Downloads’.

Our latest articles in your inbox.

Don’t miss out on any news about the sovereign cloud.

You can find information on the use of the delivery service provider Brevo, the logging of logins and your right of withdrawal in our privacy policy.

Contents
Contact
Social
cloudahead Ki Park Logo