Writing
Notes on data platform architecture. Mostly the decisions rather than the technology, because the technology changes and the decisions rhyme.
First post coming shortly. What is queued:
- Resolving one person across three systems that were never designed to agree
- Why a new data source should be a configuration entry, not a codebase
- Choosing a security model by its failure direction
- Rationalising overlapping data platforms by capability fit rather than list price
- What twenty years of integration work teaches you about trusting a number
To add a post: copy
writing/_template.html into writing/your-post-slug/index.html,
write it, then add a row to the list on this page. No build step, no dependencies.