Device Driver
The small program that translates general system requests into instructions one specific component understands.
Glossary
Translation Layer
The conceptual boundary where one language is converted into another so two unlike systems can cooperate.
In one line
The conceptual boundary where one language is converted into another so two unlike systems can cooperate.
Also calledshimcompatibility layer
A translation layer is any place in a computer where requests are rewritten from one form into another. A driver is a clear example, but the idea appears throughout computing wherever two parts need to work together without speaking the same language. One side states what it wants; the layer restates that wish in terms the other side can act on.
The value of a translation layer is that each side can change independently. As long as both still meet at the agreed boundary, neither has to know the inner details of the other. A component can be redesigned entirely, and the rest of the system carries on unaffected, because the layer absorbs the difference.
This independence is what makes large systems possible to build and maintain. Without translation layers, every part would be tangled directly into every other part, and a single change would ripple everywhere. With them, complexity is divided into tidy compartments that can be understood, tested, and improved one at a time.
A good translation layer is almost invisible. It adds just enough effort to bridge two worlds and no more, so the cooperation it enables feels effortless even though a quiet, careful conversion is happening every time a request passes through.
In practice
In practice, imagine two people working together through an interpreter. One asks a question in their own language, the interpreter restates it, and the answer comes back the same way. Neither speaker has to learn the other's grammar; they simply trust the person in the middle to carry the meaning faithfully, which is exactly what a translation layer does for software.
