Service / 05
Database architecture
We model data deliberately, then plan the indexes, migrations, replication and recovery needed to keep it dependable.
Start a projectordersprimary
iduuid · pk
customer_iduuid · fk
statusenum
total_centsint
created_attimestamptz
customersreference
iduuid · pk
nametext
emailcitext
segmenttext
order_itemsdetail
iduuid · pk
order_iduuid · fk
skutext
quantityint
price_centsint
orders.customer_id → customers.idorder_items.order_id → orders.id
The work
Designed for
the conditions.
- 01Data modelling
- 02Schema and index design
- 03Query optimisation
- 04Migrations
- 05Replication and recovery
Process
Clear steps,
visible progress.
Model the domain
Name the entities and relationships the business runs on.
Design for the queries
Shape schemas and indexes around real access patterns.
Plan for growth
Migrations, partitioning and capacity before they hurt.
Protect the data
Replication, backups and tested recovery paths.
The work
What you get
- 01Data model and ER diagrams
- 02Index and query tuning report
- 03Migration and rollback plan
- 04Backup and recovery drills
Operating targets
Tested RPO/RTO
Recovery
Query budgets
Performance
Encrypted at rest
Security
Live example
Edit the code. Run it. Break it.
A real, runnable slice of this work — your edits run in a sandboxed preview.
playground/database-architecture.html
sandbox.nordiso.local/database-architecture
sandbox idle — boots when this section scrolls into view
Technology examples
Examples, not a fixed stack — chosen per project, with the team that will own it.
