Sources, Store and Clients

Mon, 01 Jan 0001 00:00:00 +0000

Sources, Store and Clients

A first picture, drawn before anything is built. It shows the shape the requirements so far describe, and will change as they settle.

Sources

Where the owner’s music is kept today. Each stays the truth for what it holds.

Where It Runs

Mon, 01 Jan 0001 00:00:00 +0000

Where It Runs

eds-inventory runs in EdS’s Deevnet IoTaaS tenant, beside EdS’s own services. It is its own project, in its own repository, with its own releases; it shares a tenant with its first client, not a codebase.

Why the same tenant

A tenant has no way in. Deevnet IoTaaS’s tenant fabric has no inbound path by design (Deevnet ADR-0001, Deevnet ADR-0003); it is why EdS’s broker lives outside EdS’s tenant. A service in another tenant could not be asked over HTTP by EdS’s services without a path Deevnet IoTaaS does not offer. In the same tenant, EdS asks the inventory as lightd asks palette: one service to another, on the same network.
Nothing is invented for it. No new path between tenants, and no Deevnet IoTaaS decision to wait on.

Sharing a tenant does not change the boundary. The inventory still knows nothing about EdS, and is still reached only through its contract.

Architecture on eds-inventory

Sources, Store and Clients

Sources, Store and Clients

Sources

Where It Runs

Where It Runs

Why the same tenant