Home / Articles / Simplified, or outsourced? A reply to Nadzeya Stalbouskaya on removing servers and databases / Versions / v1.4.0
Simplified, or outsourced? A reply to Nadzeya Stalbouskaya on removing servers and databases: what changed in v1.4.0
From v1.3.0 (2026-10-25, a2736ecb7) to v1.4.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 3 changed in place, 32 unchanged. About 0 words added and 159 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot nz-thread.webp | images/ | The threadLinkedIn on LinkedIn:thread: my reply to Stephan Bitton, that my strategy has been to have no databases, run serverless services and now no server-side code I maintain,Bitton and Nadzeya Stalbouskaya's challenge:challenge removing databases and server-side code does not necessarily remove complexity; sometimes it moves it into external services we do not fully control. "How do you distinguish between genuinelyon simplifying architectureor and simply outsourcing its complexity?"outsourcing. | small | aside
12 unchanged paragraphs, under In short {#in-short}, The question {#question}, Map it {#map}
!shot wm-three.webp | images/ | Three moves to the right,right mapped:on the map: our own login, with passwords, resets and a password database, moved to passkeys, which every major browser and platform supports; our own database server, with on-call, failoverserver and upgrades, moved to object storage and static hosting; and our own version of a feature moved to a young startup's service, which looks like a commodity on our map but rests on its own early code and its own suppliers. Positions are illustrative.startup. | concept
7 unchanged paragraphs, under Where our own products sit {#ours}, Who would certify it? {#certify}
!shot wm-certify.webp | images/ | Maturity is what can be certified, insured and held to an SLA:SLA, explorer,shown genesisfrom andexplorer custom, glued together, which nobody should certify or will insure; villager, product, which works and is used, certifiable in parts, where SG/Send sits;to town planner, commodity and utility, stable by design, documented, with a track record and high SLAs, where passkeys sit. Rising with maturity: security, stability, reliability, disaster recovery, resilience, documentation, SLAs, insurability and certifiability.planner. | concept
11 unchanged paragraphs, under What this does not claim {#limits}, Where this comes from {#sources}