I recently came across the naming convention "_OAPI" when naming an "_API" module that uses service actions instead of consuming/exposing a REST API. What does the "O" in "OAPI" mean?
The module in question reads data from an external system to be used in various core modules, mainly my "CS" module. It is simply reading data from an external database, so it bridges the gap between my extension modules that include the external tables and the "CS" module (it is a module that offers service actions that are reusable, at least in theory, to be used by my application's "CS" module but potentially other applications for querying data from the external system's database).
For additional context, there is a "sibling" module that actually exposes REST APIs - these APIs are POST endpoints that allow my application to submit data to the external system. Again, this contrasts with the module that I think should be suffixed "_OAPI" in that it uses service actions to read data from the external system's database.
Referenced these resources:
Hi JD136 ,
OAPI = Outsystems Application Program Interface. It's called like that because Services in Outsystems are REST endpoints, allowing to have weak dependencies between modules.
The answer to this is also featured in OutSystem's service action best practices deck (see page 24), courtesy of @André Pimenta.
A colleague of mine thinks the "O" means "OutSystems".
Another reference: