<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Bolt on Momo Engineering Journal</title><link>/tags/bolt/</link><description>Recent content in Bolt on Momo Engineering Journal</description><image><title>Momo Engineering Journal</title><url>/images/og-image.png</url><link>/images/og-image.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 28 Oct 2026 17:47:15 -0600</lastBuildDate><atom:link href="/tags/bolt/index.xml" rel="self" type="application/rss+xml"/><item><title>⚡ Bolt: Zero-Allocation SigV4 Canonical Headers</title><link>/posts/057-bolt-sigv4-zero-alloc-headers/</link><pubDate>Thu, 15 Oct 2026 11:43:50 +0000</pubDate><guid>/posts/057-bolt-sigv4-zero-alloc-headers/</guid><description>Every authenticated S3 request rebuilds a SigV4 canonical-headers block — and the two obvious ways to write it (strings.Split and Header.Get) each allocate on the hottest authorization path. This post walks through replacing both with an IndexByte scan and an EqualFold lookup, and the golden-equivalence test that proves the rewrite is byte-identical for every request AWS clients actually send.</description></item><item><title>S3 Versioning on a Content-Addressed Store: Two Kinds of Identity</title><link>/posts/056-s3-versioning-on-cas/</link><pubDate>Sun, 11 Oct 2026 08:56:13 +0000</pubDate><guid>/posts/056-s3-versioning-on-cas/</guid><description>Why S3 versioning and content-addressed storage seem to conflict — mutation identity vs content identity — and how momo keeps both: UUIDv4 version records pointing at deduplicated blobs, delete markers that shadow without deleting, and pagination that can only be computed after sorting. Teaches: the real semantics backup tools depend on, and where the version chain deliberately stops being distributed.</description></item><item><title>⚡ Bolt: Zero-Allocation Parsing of ETag Lists</title><link>/posts/052-bolt-etag-matches-zero-alloc/</link><pubDate>Tue, 06 Oct 2026 11:16:37 +0000</pubDate><guid>/posts/052-bolt-etag-matches-zero-alloc/</guid><description>How we removed the heap allocation from ETag list parsing on the S3 conditional-request path by replacing strings.Split with a strings.IndexByte scan. Teaches: what If-Match/If-None-Match actually carry, why Split allocates per request, and how a microbenchmark proves the win.</description></item><item><title>🐜 Adaptive Systems: Ant-Colony Routing and Epigenetic Concurrency</title><link>/posts/052-adaptive-systems-foundations/</link><pubDate>Tue, 06 Oct 2026 05:19:24 +0000</pubDate><guid>/posts/052-adaptive-systems-foundations/</guid><description>How Momo replaces static concurrency limits and rigid replica selection with bio-inspired adaptive mechanisms: Ant Colony pheromone-based replica exploration and Epigenetic host-capacity admission.</description></item><item><title>⚡ Bolt: Zero-Allocation Parsing of AWS Chunked Headers</title><link>/posts/051-bolt-aws-chunked-zero-alloc/</link><pubDate>Thu, 01 Oct 2026 11:32:41 +0000</pubDate><guid>/posts/051-bolt-aws-chunked-zero-alloc/</guid><description>How we removed the last heap allocation from the aws-chunked ingest path by replacing strings.Split and strings.TrimPrefix with a strings.IndexByte scan. Teaches: what a streaming S3 upload body looks like, why Split allocates per chunk, and how a microbenchmark proves the win.</description></item><item><title>⚡ Bolt: Eliminating the Last Remaining S3 XML Time Allocation</title><link>/posts/048-bolt-listparts-appendformat/</link><pubDate>Tue, 08 Sep 2026 11:29:58 +0000</pubDate><guid>/posts/048-bolt-listparts-appendformat/</guid><description>How we eliminated the final per-response heap allocation in S3 XML rendering by swapping time.Format for time.AppendFormat in the ListParts handler. Teaches: the stack-buffer time formatting pattern, why Format allocates, and how microbenchmarks prove the win.</description></item><item><title>FUSE Transport: Migrating to go-fuse/v2</title><link>/posts/029-fuse-go-fuse-v2-migration/</link><pubDate>Tue, 01 Sep 2026 18:40:07 +0000</pubDate><guid>/posts/029-fuse-go-fuse-v2-migration/</guid><description>The momofs FUSE mount traded its hand-rolled bazil.org/fuse adapter for the go-fuse/v2 high-level fs API, mapped all 22 node callbacks to go-fuse interfaces, and deprecated consistency=cached.</description></item><item><title>⚡ Bolt: Zero-Allocation Last-Modified Headers</title><link>/posts/045-bolt-lastmodified-header/</link><pubDate>Tue, 01 Sep 2026 11:19:08 +0000</pubDate><guid>/posts/045-bolt-lastmodified-header/</guid><description>time.Format allocates a fresh string on every S3 GET/HEAD response. Swapping to time.AppendFormat drops that heap escape to zero — measured 32 B/op saved per request on the hottest read path.</description></item><item><title>⚡ Bolt: Eliminating Time Formatting Allocations in S3 HTTP Responses</title><link>/posts/047-bolt-s3-copyresult-time-alloc/</link><pubDate>Sun, 30 Aug 2026 11:20:58 +0000</pubDate><guid>/posts/047-bolt-s3-copyresult-time-alloc/</guid><description>How we optimized S3 XML responses by replacing time.Format with time.AppendFormat to eliminate heap allocations. Teaches: stack-buffer time formatting pattern, hot path identification via pprof.</description></item><item><title>The Benchstat Gauntlet: Performance Regressions as CI</title><link>/posts/025-benchmark-benchstat-gate/</link><pubDate>Fri, 28 Aug 2026 00:32:50 +0000</pubDate><guid>/posts/025-benchmark-benchstat-gate/</guid><description>Base-vs-branch benchmark comparison gates every PR — plus the runner-noise saga (S3PutSpool, LocalWrite, allowlist, apostrophe) that made it honest.</description></item><item><title>Reducing Read-Verify Hashing: Trust Earned by Real Verification</title><link>/posts/043-reduce-read-verify-hashing/</link><pubDate>Wed, 26 Aug 2026 19:00:59 +0000</pubDate><guid>/posts/043-reduce-read-verify-hashing/</guid><description>Verify-on-read re-hashes the full object on every local read (~8x slower than write). A ReadVerifier seam skips re-verification for blobs verified this process, while scrub still catches bitrot.</description></item><item><title>Perf Profiling Baseline: Measure Before You Optimize — and Keep pprof Off the Wire</title><link>/posts/042-perf-profiling-baseline/</link><pubDate>Wed, 26 Aug 2026 17:46:56 +0000</pubDate><guid>/posts/042-perf-profiling-baseline/</guid><description>Phase-0 profiling harness via go test -cpuprofile/-memprofile; Rule 75 forbids networked pprof on unauthenticated listeners. The baseline proved stdlib SHA-256 already uses AVX2.</description></item><item><title>Seams, Not Plugins: A Fast Path That Stays Concrete</title><link>/posts/044-plugin-seam-architecture/</link><pubDate>Wed, 26 Aug 2026 16:45:18 +0000</pubDate><guid>/posts/044-plugin-seam-architecture/</guid><description>Adaptive behaviors use compile-time Go interface seams injected at decision points — not dynamic plugins. The fast path stays concrete; the trust core stays auditable; policy is declarative.</description></item><item><title>Metrics and Observability: Per-Node Bind, Prometheus Export</title><link>/posts/026-metrics-observability/</link><pubDate>Tue, 25 Aug 2026 06:12:59 +0000</pubDate><guid>/posts/026-metrics-observability/</guid><description>Prometheus metrics export with a per-node metrics_host/metrics_port bind — observability that scales past the &amp;lsquo;just scrape node 0&amp;rsquo; era.</description></item><item><title>R5 Metrics Phases 2-4: Storage, P2P, and Latency Histograms</title><link>/posts/032-r5-metrics-phases-2-4/</link><pubDate>Tue, 25 Aug 2026 03:25:22 +0000</pubDate><guid>/posts/032-r5-metrics-phases-2-4/</guid><description>R5 Phases 2-4 shipped: storage metrics (disk, CAS, GC), P2P metrics (SWIM, leases, scatter-gather), and opt-in latency histograms — all with &amp;lt;1% overhead via sync/atomic counters.</description></item><item><title>At-Rest Integrity: Verify-on-Read, Checksums, and GC</title><link>/posts/007-at-rest-integrity-and-gc/</link><pubDate>Mon, 24 Aug 2026 19:36:43 +0000</pubDate><guid>/posts/007-at-rest-integrity-and-gc/</guid><description>CAS keys make verify-on-read free: central verification, x-amz-checksum echo, tombstone GC, and corruption surfacing.</description></item><item><title>Centralized Integrity Verification: Checksums Move to the Storage Core</title><link>/posts/031-core-integrity-verification/</link><pubDate>Mon, 24 Aug 2026 18:03:31 +0000</pubDate><guid>/posts/031-core-integrity-verification/</guid><description>S3 integrity checksums moved from a surface-level adapter into the storage/ingest core via a protocol-agnostic ChecksumProvider seam — every write path verified, replicas re-verify on receive.</description></item><item><title>⚡ Bolt: 1000 → 16 Allocations in S3 ListObjectsV2 XML</title><link>/posts/036-s3-listxml-appendformat-optimization/</link><pubDate>Mon, 24 Aug 2026 11:24:01 +0000</pubDate><guid>/posts/036-s3-listxml-appendformat-optimization/</guid><description>S3 ListObjectsV2 XML serialization dropped from ~1000 allocations to 16 per op via inlined time formatting and a pre-allocated escape buffer.</description></item><item><title>Adaptive Scaling: Gossip Fanout, Stream Chunks, Peer Quality</title><link>/posts/018-adaptive-scaling-peer-quality/</link><pubDate>Fri, 14 Aug 2026 19:43:24 +0000</pubDate><guid>/posts/018-adaptive-scaling-peer-quality/</guid><description>Three adaptive feedback loops: gossip fanout scales with cluster size, streaming chunk size adapts to cipher/memory, peer quality feeds quorum decisions.</description></item><item><title>⚡ Bolt: Zero-Allocation and Hot-Path Engineering</title><link>/posts/024-bolt-performance-engineering/</link><pubDate>Wed, 12 Aug 2026 11:40:41 +0000</pubDate><guid>/posts/024-bolt-performance-engineering/</guid><description>The Bolt mindset codified: no heap escapes in hashing/encoding, deadline amortization cuts SetDeadline ~98%, allocation hotspots hunted by profile. Teaches: zero-escape patterns, measurement contracts, trade-off posture.</description></item><item><title>AWS Chunked Streaming: Signed Payloads Without Buffering</title><link>/posts/040-aws-chunked-streaming/</link><pubDate>Tue, 11 Aug 2026 04:52:58 +0000</pubDate><guid>/posts/040-aws-chunked-streaming/</guid><description>aws-chunked payload encoding streams large S3 uploads in signed chunks — no full-body buffering, per-chunk SigV4 integrity.</description></item><item><title>Transport Evolution: TCP, QUIC, and the Wire Protocol</title><link>/posts/003-transport-tcp-to-quic/</link><pubDate>Tue, 11 Aug 2026 04:02:50 +0000</pubDate><guid>/posts/003-transport-tcp-to-quic/</guid><description>Momo&amp;rsquo;s transport layer grew from TCP to a QUIC/TLS 1.3 fan-out — fixing handshake, ACK framing, deadlines, and TLS identity along the way.</description></item><item><title>Pluggable Storage Backends: local, nfs, s3, raw</title><link>/posts/006-pluggable-storage-backends/</link><pubDate>Sun, 26 Jul 2026 14:33:59 +0000</pubDate><guid>/posts/006-pluggable-storage-backends/</guid><description>The &lt;code&gt;[storage] backend&lt;/code&gt; seam swaps blob storage (local, nfs, s3, raw) behind one Store interface, keeping CAS metadata local.</description></item><item><title>External S3 Client Replication Downgrade: When aws-cli Can't Fan Out</title><link>/posts/030-external-s3-client-replication-downgrade/</link><pubDate>Wed, 01 Jul 2026 23:36:39 +0000</pubDate><guid>/posts/030-external-s3-client-replication-downgrade/</guid><description>External S3 clients like aws-cli don&amp;rsquo;t send momo headers — the server detects this and downgrades client-side replication modes to server-side alternatives, ensuring replication never silently drops.</description></item><item><title>CRUSH-lite: Deterministic Weighted Placement</title><link>/posts/005-crush-placement/</link><pubDate>Tue, 30 Jun 2026 13:09:01 +0000</pubDate><guid>/posts/005-crush-placement/</guid><description>Weighted rendezvous hashing picks replicas deterministically and peer-equally without a central allocator — later hardened for failure domains. Teaches: content-hash-based placement, weighted rendezvous hashing, deterministic stable sort, failure domain filtering.</description></item><item><title>🛡 Zero-Crash Hardening: Defensive Patterns for a Networked Object Store</title><link>/posts/037-zero-crash-hardening-patterns/</link><pubDate>Wed, 03 Jun 2026 06:03:39 +0000</pubDate><guid>/posts/037-zero-crash-hardening-patterns/</guid><description>Systematic defensive coding: nil-safety, numeric overflow guards, resource lifecycle discipline, panic recovery at every boundary, and concurrency safety under -race.</description></item><item><title>Replication Strategies and the Polymorphic Engine</title><link>/posts/002-replication-strategies-polymorphic/</link><pubDate>Mon, 04 May 2026 18:54:37 +0000</pubDate><guid>/posts/002-replication-strategies-polymorphic/</guid><description>Chain, Splay, and Primary-Splay replication — and the metrics-driven controller that switches between them at runtime.</description></item><item><title>CAS: Content-Addressable Storage and Deduplication</title><link>/posts/004-cas-content-addressable-store/</link><pubDate>Wed, 11 Mar 2026 14:34:18 +0000</pubDate><guid>/posts/004-cas-content-addressable-store/</guid><description>Identify every object by its SHA-256 content hash — server-side dedup, verify-on-read, and a path that later mounted a filesystem. Teaches: content addressing principles, single write chokepoint, Bolt/Sentinel patterns.</description></item></channel></rss>