As a developer goes deeper into Odoo development, certain concepts of how Odoo's framework is organised come up. Two are the registry and services. This piece introduces them.
Why these concepts come up
Odoo is a framework, and a framework has an internal organisation, a way it holds together the things it is made of. As a developer works with Odoo's framework, especially as the development goes beyond the basics, the developer meets the concepts of that internal organisation. The registry and services are two such concepts. Understanding them, at least in concept, is part of a developer genuinely working with the Odoo framework rather than just on its surface.
The registry
The registry, in Odoo, is, in concept, the organised collection of the things the framework holds. Odoo is made of many things, and the registry is how the framework holds and organises them, so they are known and available within the system. The registry is, in essence, the framework's organised record of what it is made of. A developer does not usually manipulate the registry directly in ordinary development, but understanding that the registry is how Odoo organises and holds the things it is made of is part of understanding how the framework works.
Services
A service, in Odoo, is, in concept, a provided capability that the parts of the system can use. Rather than every part of the system implementing everything it needs, certain capabilities are provided as services, available to be used by the parts that need them. A service is, in essence, a capability made available for use across the system. Services are a way Odoo's framework provides shared capabilities, so the parts of the system can use a provided capability rather than each building it. A developer, particularly in front-end development, works with services, using the capabilities they provide.
Why a developer benefits from understanding these
A developer benefits from understanding the registry and services, at least in concept, because they are part of how the Odoo framework genuinely works, and genuinely working with the framework, rather than fighting it or working only on its surface, is what good Odoo development is. A developer who understands that Odoo organises its things in the registry, and provides shared capabilities as services, has a better grasp of the framework they are building within, and builds more in keeping with how Odoo genuinely works. These concepts are part of the deeper understanding of the framework that a developer grows into.
Work with the framework
The recurring principle of Odoo development applies: work with the framework, not against it. The registry and services are part of how the framework is organised, and a developer should build in keeping with that organisation, using services as Odoo provides them, working within the framework's structure. Understanding the registry and services is part of understanding the framework well enough to work genuinely with it.
The takeaway
The Odoo registry and services are concepts of how Odoo's framework is organised. The registry is, in concept, the framework's organised collection of the things it is made of, how Odoo holds and organises them. A service is a provided capability that the parts of the system can use, a way the framework provides shared capabilities. A developer benefits from understanding these, at least in concept, because they are part of how the framework genuinely works, and genuinely working with the framework is what good Odoo development is. For how we approach Odoo, see our ERP practice.