Assessment · 26
Architecture decisions
Decisions about how systems fit together, including warehouses, business applications and the connections between them.
When this is useful
A system change can leave ownership of data or processing unclear. A useful architecture makes those responsibilities explicit and explains the choices behind them.
My contribution
I compare arrangements for the systems in scope, identify the relevant trade-offs and document decisions about sources, connections, storage and processing.
CRM, billing and product events land in separate warehouse histories. An account-ID join produces a daily customer model shared by reporting, weekly LTV scoring and daily CRM audience assignments.
What it covers
- Responsibilities of each system
- Authoritative sources and data flows
- Where transformations, calculations and other processing happen
- Options and relevant constraints
- Decisions, reasons and unresolved questions
- Dependencies affecting the proposed arrangement
The output
A proposed system arrangement and a record of its decisions, dependencies and remaining questions.
For an enquiry, describe the question and the systems involved.
contact@fiftystork.com ↗