[{"data":1,"prerenderedAt":30},["ShallowReactive",2],{"content:journal-boring-infrastructure:en":3},{"slug":4,"title":5,"date":6,"minutes":7,"excerpt":8,"body":9},"boring-infrastructure","In praise of boring infrastructure","2026-07-24",4,"The best infrastructure is the one nobody talks about, because it simply keeps working.",[10,13,16,18,20,28],{"type":11,"text":12},"p","There is a particular kind of infrastructure that makes for great conference talks: many moving parts, clever automation, a diagram that needs a second screen. There is another kind that nobody gives talks about, because it works quietly for years. We prefer the second kind.",{"type":14,"text":15},"h2","Complexity is a running cost",{"type":11,"text":17},"Every component in an infrastructure has to be understood, patched, monitored and eventually replaced. A container orchestrator is a fine tool when you operate dozens of services; for a single application with a database, it is mostly a second system to maintain.",{"type":14,"text":19},"What boring looks like",{"type":21,"items":22},"ul",[23,24,25,26,27],"Every environment can be recreated from code.","Deployments happen during working hours, because they are routine.","Backups are restored on a schedule, not just created.","Alerts fire for things customers notice, and somebody knows what to do.","A new team member can read how it all fits together in an afternoon.",{"type":11,"text":29},"None of this is novel. All of it is surprisingly rare. And it is the foundation that lets the interesting software on top do its job.",1794663560395]