Planned landscape
Databases
What is stored, and how is it related?
The datastores behind the systems — relational schemas and the document, key-value and graph stores alongside them — browsable directly, instead of reconstructed from migrations.
What it will show
- SQL stores as an entity–relationship view: tables, columns, keys and the foreign keys between them.
- NoSQL stores on their own terms — document shapes and their variants, key-value namespaces, graph node and edge types, wide-column families.
- The schema a document store actually holds, inferred from the data, since there is rarely a declaration to read.
- Which service owns which store, so a shared database stops being invisible.
Where it stands
- Status
- Planned
- Rendered from
- Not yet assigned
No module is assigned yet. The hard part is not the relational half — it is describing schemaless stores honestly, without pretending a document collection is a table.
A landscape earns a panel when something renders it. Until then it says so, because a link to an empty page is worse than one that admits it is not built. Back to the landscapes