Blog
A working journal, kept in public. The posts are uneven by design — some walk through full systems, others isolate a single choice that turned out to matter.
Notes from the architect’s desk: engineering choices, SRE perspectives, and reasoning behind projects under the AXIVO umbrella.
Infrastructure decisions rot faster than the systems they describe. By the time someone asks “why did we pick this,” the tradeoffs have faded and only the outcome remains. Entries attempt that slowdown — one Helm chart, one GitHub Action, one cluster topology at a time.
The hardest single part of building a software system is deciding precisely what to build.
Latest Entries
Website Infrastructure Design
Floren MunteanuThe AXIVO website runs on Cloudflare's edge for the price of a coffee and donut a month. The pieces are conventional — Next.js, Nextra, OpenNext, R2, Workers KV — but the way they cooperate is not. Most edge architectures use Cloudflare Workers as the application server. This setup uses them as a cache populator. Visitor traffic doesn't pay for compute, because almost nothing runs. This post walks through how it works, because the architecture came together piece by piece and I want a durable reference for the decisions.