Insights
Architecture notes, delivery lessons and sober takes on distributed ledgers, from the engineers who build the systems.
Featured
Many of the blockchain proposals we review would be better served by a well-designed database, a signed API or an append-only log. Here are the four questions we ask first, the alternatives we recommend most often, and the cases where a distributed ledger does earn its place.
Many of the blockchain proposals we review would be better served by a well-designed database, a signed API or an append-only log. Here are the four questions we ask first, the alternatives we recommend most often, and the cases where a distributed ledger does earn its place.
Before we write code, we write down the decisions: context, constraints, options and trade-offs. What our architecture dossier contains, and how clients use it after handover.
Token standard, network topology, custody model and admin tooling: the early choices that decide whether a tokenization platform clears compliance review and scales beyond its pilot.
Strangler-fig migration, change data capture and parallel runs let you replace a core system in phases, while the business keeps running on it.
Tracing, metrics and alerting cost least when added during the build. What we instrument with OpenTelemetry from day one, and how it shortens incidents after launch.
Documentation, test evidence, runbooks and support terms belong in the statement of work. What we commit to in writing, and why it lowers the cost of ownership.
Nothing filed under “All” yet.
We publish about one piece a month. Subscribe below and the next one will reach you, or read everything we have so far.
Authors
