Six architecture decisions behind NovaDesk
The operations platform we built for ourselves runs on one process, one database and one file volume. Here is why, decision by decision.
Insights
How we build, written down.
Architecture decisions, operating practice and technical choices, written from the products we build and run — reasons included.
Latest articles
Native, cross-platform or web: choosing the first version of your app
The right technology for a first version follows from a few constraints — distribution, purchases, device features and the team that will maintain it.
Shipping is half the work: what an operating contract should cover
An application lives for years after launch. Six things an operating contract should cover, and the questions to ask before you sign one.
Index
By topic.
3 articles, newest first within each topic.
Where these notes come from.
Every article draws on a product we build or run. NovaDesk is described with its real architecture; the advice on contracts and technology choices is the advice we give in scoping.
Have something worth building?
Tell us what you’re building. We reply within two working days with an honest first view on feasibility, scope and order of magnitude.