A single unit or separate services
The two topologies of CIAS next to CDMS: embedded in one process or as a separate service. What runs in each, who calls whom, why both must behave the same in the subject area — and how that relates to the operating mode of the data storage, SINGLE or MULTI.
Topics in this subject area
- 1.CIAS embedded (a single unit)
CIAS runs in the same process as CDMS or the hub backend. Which modules are included, how CDMS calls CIAS, and which database CIAS uses.
- 2.CIAS as a separate service
CIAS runs as its own service. What the CDMS service then brings along itself, which calls go over HTTP, and with which token.
- 3.Embedded and standalone compared
All differences between “CIAS in the same process” and “CIAS as a separate service” in one overview: artifacts, calls, database, failure behavior and the delay of a suspension.
- 4.Configuration decides what runs
Every CIAS module sits behind a switch with no default value. Why no CIAS class activates itself, and what is decided at build time (which provider adapter).
- 5.SINGLE and MULTI across both modules
What the data storage operating mode does in CDMS and in CIAS, and that the same switch also decides whether the tenant in the token is checked.
- 6.Why both modes must behave the same in the subject area
Same code, same rules, same refusals. What “functionally identical” means in practice, where the difference does show, and where it does not.