<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Monorepo on miti99</title><link>https://miti99.com/en/tags/monorepo/</link><description>Recent content in Monorepo on miti99</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 16 Nov 2026 17:39:19 +0700</lastBuildDate><atom:link href="https://miti99.com/en/tags/monorepo/index.xml" rel="self" type="application/rss+xml"/><item><title>Newsletter #57</title><link>https://miti99.com/en/post/2025/09/30/</link><pubDate>Tue, 30 Sep 2025 00:00:00 +0700</pubDate><guid>https://miti99.com/en/post/2025/09/30/</guid><description>&lt;p&gt;&lt;em&gt;&lt;del&gt;This post was created using &lt;a href="https://github.com/musistudio/claude-code-router" rel="noopener noreferrer"&gt;Claude Code Router&lt;/a&gt; with the &lt;code&gt;qwen3-coder&lt;/code&gt; model running on &lt;a href="https://platform.iflow.cn/docs/api-mode" rel="noopener noreferrer"&gt;iFlow Platform&lt;/a&gt;.&lt;/del&gt; Enjoy Newsletter #57.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="agentic-ai-has-changed-my-career"&gt;&lt;a href="https://medium.com/@elliotgraebert/agentic-ai-has-changed-my-career-2c6e3dd29708" rel="noopener noreferrer"&gt;Agentic AI has changed my career&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Elliot Graebert, a director of engineering at Skydio, confesses that for most of his career he barely wrote code because he moved into management too early. About four months ago, he started &amp;ldquo;vibe coding&amp;rdquo; directly in the multi-million-line monorepo that powers the company&amp;rsquo;s drone fleet, and he is now among its top five contributors, sometimes submitting up to ten pull requests per hour. He distinguishes between two approaches: vibe coding is like pair programming with AI (using tools like Windsurf or Cursor), where the loop is measured in seconds and requires constant attention; agentic AI is like delegating to an eager intern, where the loop is measured in minutes and you only check back once the task is done. His journey went from 0.5x speed (fixing small UI bugs in a single editor), to 1.5x by running three environments in parallel with Gemini, Claude, and GPT to &amp;ldquo;swarm&amp;rdquo; a tough bug, and then to 3x thanks to context files (Windsurf Rules) documenting code conventions and test commands, refined iteratively whenever the AI got stuck.&lt;/p&gt;
&lt;p&gt;The jump to 10x came from Coder Tasks—automated environments that go from prompt to pull request—combined with two MCPs: GitHub to read issues and open pull requests (triggering CI and Vercel previews), and Playwright so the AI can launch a browser, reproduce a bug, fix it, and verify the fix itself. The core lesson is that agentic AI succeeds when it has a feedback loop that does not require a human in the middle; at that point, he can run dozens of tasks at once, such as completing an entire data-filter component migration in a single day. He also stresses that AI does not magically solve everything—you have to invest in tooling—and the most exciting result is that designers, product managers, and even the flight test team can now contribute directly to the product.&lt;/p&gt;
&lt;h2 id="the-evolution-of-garbage-collectors-from-javas-cms-to-zgc-and-a-jvm-vs-go-vs-rust-latency-shootout"&gt;&lt;del&gt;&lt;a href="https://codemia.io/blog/path/The-Evolution-of-Garbage-Collectors-From-Javas-CMS-to-ZGC-and-a-JVM-vs-Go-vs-Rust-Latency-Shootout" rel="noopener noreferrer"&gt;The Evolution Of Garbage Collectors From Javas CMS To ZGC And A JVM Vs Go Vs Rust Latency Shootout&lt;/a&gt;&lt;/del&gt;&lt;/h2&gt;&lt;p&gt;&lt;del&gt;Memory management is a critical topic in programming, especially in languages like Java, Go, and Rust. This article explores the evolution of garbage collectors (GCs) from Java&amp;rsquo;s traditional Concurrent Mark-Sweep (CMS) to the modern Z Garbage Collector (ZGC).&lt;/del&gt;&lt;/p&gt;
&lt;p&gt;&lt;del&gt;ZGC is a major leap forward in minimizing application pause times, aiming to keep pauses under 10ms regardless of heap size. This makes a dramatic performance difference compared to earlier-generation GCs like CMS.&lt;/del&gt;&lt;/p&gt;
&lt;p&gt;&lt;del&gt;The article also compares latency performance across platforms:&lt;/del&gt;
&lt;del&gt;- JVM (with ZGC): Significantly reduced pause times thanks to improvements in GC design&lt;/del&gt;
&lt;del&gt;- Go: Efficient low-latency GC powered by a concurrent algorithm and tri-color marking&lt;/del&gt;
&lt;del&gt;- Rust: Avoids GC entirely through its ownership model, delivering predictable performance without GC overhead&lt;/del&gt;&lt;/p&gt;
&lt;p&gt;&lt;del&gt;&lt;strong&gt;Key takeaways:&lt;/strong&gt;&lt;/del&gt;
&lt;del&gt;- ZGC keeps application pause times under 10ms&lt;/del&gt;
&lt;del&gt;- Go uses an efficient marking algorithm to keep latency low&lt;/del&gt;
&lt;del&gt;- Rust eliminates the need for GC altogether through its ownership model&lt;/del&gt;
&lt;del&gt;- Language choice significantly impacts performance and user experience&lt;/del&gt;&lt;/p&gt;
&lt;h2 id="new-in-java25-generational-shenandoah-gc-is-no-longer-experimental"&gt;&lt;del&gt;&lt;a href="https://theperfparlor.com/2025/09/14/new-in-java25-generational-shenandoah-gc-is-no-longer-experimental/" rel="noopener noreferrer"&gt;New in Java25: Generational Shenandoah GC is no longer experimental&lt;/a&gt;&lt;/del&gt;&lt;/h2&gt;&lt;p&gt;Java 25 officially graduates Generational Shenandoah from experimental status, making it ready for production use. Shenandoah is a low-pause-time garbage collector introduced in Java 12 that runs mostly concurrently with the application. Its generational mode, introduced experimentally in Java 24, separates heap memory into young and old generations. Because most objects die young, this separation spares the collector from repeatedly scanning long-lived objects unnecessarily, improving performance and reducing memory footprint.&lt;/p&gt;
&lt;p&gt;In Java 25, the feature has been stabilized with numerous bug fixes, lower garbage collection overhead, more efficient memory region management, and improved tooling and logging. According to the article, these improvements make Generational Shenandoah mature enough for real-world applications, and you no longer need the &lt;code&gt;-XX:+UnlockExperimentalVMOptions&lt;/code&gt; flag to enable it. It marks an important milestone in Java&amp;rsquo;s ongoing garbage collection optimization journey.&lt;/p&gt;
&lt;h2 id="if-all-the-world-were-a-monorepo"&gt;&lt;a href="https://jtibs.substack.com/p/if-all-the-world-were-a-monorepo?utm_source=tldrnewsletter" rel="noopener noreferrer"&gt;If all the world were a monorepo&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Julie Tibshirani shares her experience with CRAN, the central package repository for R. Before accepting an update, CRAN not only checks the submitted package itself, but also runs checks across every package that depends on it. When she released &lt;code&gt;grf&lt;/code&gt; 2.0 with a breaking API change, CRAN blocked publication until the downstream package &lt;code&gt;policytree&lt;/code&gt; was updated. At first she found this unreasonable: why should she be responsible for someone else&amp;rsquo;s code? Over time, however, she realized this isn&amp;rsquo;t merely a different point on the speed-versus-stability trade-off spectrum, but a form of &amp;ldquo;radical empathy&amp;rdquo; in software maintenance: users&amp;rsquo; code is the library author&amp;rsquo;s responsibility too, much like the mindset inside a monorepo.&lt;/p&gt;
&lt;p&gt;She contrasts this with her time working on Elasticsearch, where leaving individual projects to upgrade on their own left thousands of projects stuck on old versions years later. Watching large-scale migrations at Databricks, she saw that when engineering teams took end-to-end ownership—including fixing downstream dependent code—completion rates rose dramatically. Although R packages tolerate less consistent APIs than ecosystems like npm or PyPI, users enjoy nearly painless dependency upgrades, offering a lesson worth pondering for other ecosystems.&lt;/p&gt;
&lt;h2 id="9-software-architecture-patterns-for-distributed-systems"&gt;&lt;a href="https://dev.to/somadevtoo/9-software-architecture-patterns-for-distributed-systems-2o86?=&amp;amp;aid=recZm2jVus1yqUHWw" rel="noopener noreferrer"&gt;9 Software Architecture Patterns for Distributed Systems&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;This article introduces nine common architectural patterns in distributed systems that are useful both in real-world design and in system design interviews. The communication patterns include: Peer-to-Peer, where nodes exchange data directly without a central coordinator, used in file sharing and blockchains; API Gateway, a unified entry point for backend services that handles security and load balancing in microservices architectures; Pub-Sub, which decouples message senders and receivers through a broker, well suited for real-time messaging, event-driven systems, and IoT; and Request-Response, where a client sends a request and receives a corresponding response from a server, ubiquitous in REST APIs and web applications (though the pattern does not strictly require synchronous execution).&lt;/p&gt;
&lt;p&gt;The data management and processing patterns include: Event Sourcing, which stores state as an immutable sequence of events for easy auditing and replay, commonly seen in financial systems; ETL (extract, transform, load) to consolidate data from multiple sources into a data warehouse for analytics and data migration; Batching, which groups data into batches to process all at once for higher efficiency; Streaming Processing, which processes continuous data streams in real time for finance, IoT, or cybersecurity; and Orchestration, which uses a central coordinator to manage workflows across services. Understanding the strengths and trade-offs of each pattern helps you build reliable, scalable, and maintainable systems as requirements evolve.&lt;/p&gt;
&lt;h2 id="sort-lines-in-source-code"&gt;&lt;a href="https://testing.googleblog.com/2025/09/sort-lines-in-source-code.html?=&amp;amp;aid=recV8wgDMqTb7Hwko" rel="noopener noreferrer"&gt;Sort Lines in Source Code&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Kyle Freeman&amp;rsquo;s post on the Google Testing Blog, adapted from a &amp;ldquo;Tech on the Toilet&amp;rdquo; episode, opens with a familiar scenario: you enable two-player mode on the last line of a config file, but when you run the game, the feature doesn&amp;rsquo;t show up. The culprit is that the &lt;code&gt;enable_two_players&lt;/code&gt; flag was declared twice with different values—easy to miss when lines are in random order. Simply sorting the lines places the duplicates right next to each other, exposing the bug immediately. The main takeaway is that sorted lists and source lines are easier to read, easier to maintain, and help prevent bugs.&lt;/p&gt;
&lt;p&gt;To automate this, the author introduces &lt;code&gt;keep-sorted&lt;/code&gt; (&lt;a href="http://github.com/google/keep-sorted" rel="noopener noreferrer"&gt;github.com/google/keep-sorted&lt;/a&gt;): you wrap the lines to sort with &lt;code&gt;keep-sorted start&lt;/code&gt; and &lt;code&gt;keep-sorted end&lt;/code&gt; comments, run &lt;code&gt;keep-sorted [file1] [file2] ...&lt;/code&gt;, and optionally hook it into pre-commit so it runs automatically on every commit. The tool also supports case-insensitive sorting, numeric sorting, prefix order, and regular expressions (for example, using &lt;code&gt;by_regex&lt;/code&gt; to sort a Go slice by its end-of-line comments). One important caveat: before sorting, make sure the original order doesn&amp;rsquo;t carry semantic meaning, such as dependency load order.&lt;/p&gt;
&lt;h2 id="rating-26-years-of-java-changes"&gt;&lt;a href="https://neilmadden.blog/2025/09/12/rating-26-years-of-java-changes/" rel="noopener noreferrer"&gt;Rating 26 years of Java changes&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Neil Madden looks back on 26 years of working with Java, from Java 1.1.8 in 1999 to Java 25, and gives subjective ratings to language and core library changes (skipping UI, graphics, the JVM, and GC). Top marks go to &lt;code&gt;java.util.concurrent&lt;/code&gt; (10/10), so well designed that people use it in place of the original collection classes; try-with-resources (10/10), which made exception handling far safer; Records (10/10), which he says Java &amp;ldquo;should have had all along&amp;rdquo;; UTF-8 by default (10/10), fixing thousands of character-encoding bugs at a stroke; along with Generics (8/10) and &lt;code&gt;var&lt;/code&gt; type inference (9/10). The Collections Framework gets just 4/10, lambdas 4/10 because of ugly stack traces, and switch expressions 6/10 as a pleasant minor improvement.&lt;/p&gt;
&lt;p&gt;On the flip side, NIO gets 0/10 for its convoluted API, Streams get 1/10 and are called one of modern Java&amp;rsquo;s biggest mistakes due to complexity, overpromised parallelism, and easy resource leaks, while the cryptography APIs get 1/10 for being easy to misuse. Worst of all is Modules at -10/10: massive disruption for very little practical benefit. Virtual threads are deemed promising but not yet battle-tested enough to score. The post also touches on time-based release cadences, pattern matching, and post-quantum cryptography, closing with an invitation for readers to debate his ratings.&lt;/p&gt;
&lt;h2 id="bonus-some-cool-visuals-from-bytebytego"&gt;Bonus: Some cool visuals from &lt;a href="https://bytebytego.com/" rel="noopener noreferrer"&gt;ByteByteGo&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;&lt;img src="https://substack-post-media.s3.amazonaws.com/public/images/aa5ea98b-c832-429d-8e48-63f25b7feb5a_3000x3900.jpeg" alt="Python vs Java"&gt;
&lt;img src="https://substack-post-media.s3.amazonaws.com/public/images/4863d93c-ca2a-4b5a-b0b4-fe3621a6c184_2250x2920.png" alt="Design Patterns Cheat Sheet"&gt;
&lt;img src="https://substack-post-media.s3.amazonaws.com/public/images/d6d04f12-2adc-4d8e-a9ca-2de16399066f_2250x3376.png" alt="Design Patterns Cheat Sheet"&gt;
&lt;img src="https://substack-post-media.s3.amazonaws.com/public/images/a370bb6a-82d3-45ad-b6f4-a2a9a4317402_800x1099.jpeg" alt="CI/CD Simplified Visual Guide"&gt;
&lt;img src="https://substack-post-media.s3.amazonaws.com/public/images/5d9faeeb-3428-44c8-94fd-4b52fc287da3_3000x3900.png" alt="How Apache Kafka Works?"&gt;
&lt;img src="https://substack-post-media.s3.amazonaws.com/public/images/45136e24-79ee-4c6d-a53a-89df6afebef6_3000x3900.png" alt="Load Balancers vs API Gateways vs Reverse Proxy"&gt;
&lt;img src="https://substackcdn.com/image/fetch/$s_!4Uyj!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1a1213e2-86cb-4fa8-bf72-e37ffe0da44d_2250x2624.heic" alt="Understanding Load Balancers: Traffic Management at Scale"&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Overall, the output is concise and I&amp;rsquo;m fairly satisfied—probably around 80% compared to Claude Code with Claude models, and since it&amp;rsquo;s free I&amp;rsquo;m very happy with it :)))&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;This post was rewritten by Claude Code with Opus 5.5 on 27/09/2026; reviewed and edited by Codex with GPT 6.1 Sol on 09/11/2026, and re-verified by Claude Code with Sonnet 5.5 on 16/11/2026.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Newsletter #54</title><link>https://miti99.com/en/post/2025/09/10/</link><pubDate>Wed, 10 Sep 2025 00:00:00 +0700</pubDate><guid>https://miti99.com/en/post/2025/09/10/</guid><description>&lt;p&gt;&lt;em&gt;&lt;del&gt;Since my personal finances haven&amp;rsquo;t been great lately, I decided to cancel my Claude subscription and am no longer using Claude Code. Right now I&amp;rsquo;m using Roo Code with the Z.AI: GLM 4.5 Air model via OpenRouter.&lt;/del&gt; Hopefully the post is still high enough quality for you all. Enjoy Newsletter #54.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="controlling-the-rollout-of-large-scale-monorepo-changes"&gt;&lt;a href="https://www.uber.com/in/en/blog/controlling-the-rollout-of-large-scale-monorepo-changes/" rel="noopener noreferrer"&gt;Controlling the Rollout of Large-Scale Monorepo Changes&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;At Uber, source code is organized into a few massive monorepos—one per major programming language—and most microservices deploy to production automatically via continuous deployment. This raises a thorny question: when a single commit can touch thousands of services—say, upgrading an RPC library used by nearly every Go service—how do you contain the blast radius if that change introduces a bug? An analysis of 500,000 commits in Uber&amp;rsquo;s Go monorepo showed that 1.4% of commits affected more than 100 services and 0.3% affected more than 1,000 services, meaning several changes every week touch a huge slice of production. Even when individual services detect failures and roll back automatically, a bug can still slip into production on services whose checks didn&amp;rsquo;t catch it.&lt;/p&gt;
&lt;p&gt;Uber&amp;rsquo;s solution is cross-service rollout orchestration. The team added a new rollout gate to the commit promotion pipeline: an asynchronous worker maintains a state machine for each large-scale commit, grouping affected services by criticality from tier 5 down to tier 0, and unlocking a more critical tier only after a required percentage of services in the preceding tier have deployed successfully. If the failure rate exceeds a threshold, the commit is flagged as unhealthy, the author is notified immediately, and further rollouts are blocked until a fix lands. Because the initial parameters were too conservative—blocking tier 1 services for up to 40 hours—the team built a simulator backed by historical deployment data to tune the thresholds, hitting their target of unlocking all tiers within 24 hours, with real-world results matching the simulation. The same mechanism is now also used to progressively roll out hundreds of machine learning model-serving services that differ only by configuration.&lt;/p&gt;
&lt;h2 id="string-length"&gt;&lt;a href="https://hsivonen.fi/string-length/" rel="noopener noreferrer"&gt;String Length&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Henri Sivonen pushes back against the popular meme mocking JavaScript because &lt;code&gt;&amp;quot;🤦🏼‍♂️&amp;quot;.length&lt;/code&gt; evaluates to 7. That emoji actually consists of five Unicode scalar values (a base character, a skin-tone modifier, a zero-width joiner, the male sign, and a variation selector), meaning the exact same string has at least four valid &amp;ldquo;lengths&amp;rdquo;: 17 UTF-8 code units (Rust), 7 UTF-16 code units (JavaScript, Java), 5 scalar values (Python 3), and 1 extended grapheme cluster (Swift). The first three numbers are fixed for any valid string and can be computed without lookup tables, whereas the grapheme cluster count depends on which version of the Unicode database the runtime bundles—so two programs can legitimately count different lengths for the same string.&lt;/p&gt;
&lt;p&gt;The author argues that reporting length in the string&amp;rsquo;s native storage code units makes complete sense, because that is the exact number needed for memory allocation and fast string concatenation, whereas higher-level counts should only be computed on demand. In his view, UTF-8 is the best internal representation, O(1) random access by scalar value is rarely needed in practice, Swift&amp;rsquo;s approach isn&amp;rsquo;t necessarily right for every language, and Python 3&amp;rsquo;s representation gives the worst trade-off. The closing section examines why applications measure string length in the first place: estimating display width (where terminals rely on East Asian Width, giving CJK characters two cells) and enforcing fair character limits across languages, illustrated through length statistics from translations of the Universal Declaration of Human Rights and Twitter&amp;rsquo;s rule counting each CJK character or emoji as two units.&lt;/p&gt;
&lt;h2 id="an-illustrated-guide-to-oauth"&gt;&lt;a href="https://www.ducktyped.org/p/an-illustrated-guide-to-oauth/" rel="noopener noreferrer"&gt;An Illustrated Guide to OAuth&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Aditya Bhargava explains OAuth with clear illustrations, starting from its origin story: in 2007, Twitter needed a way for third-party apps to post tweets on a user&amp;rsquo;s behalf without the user handing over their password. The core building block of OAuth is the access token, which acts like a user-specific, scoped API key. Using the example of the budgeting app YNAB connecting to Chase Bank, the article walks through the two-step flow: the user logs in at Chase and approves the requested permissions (scopes), after which Chase redirects back to YNAB with a short-lived authorization code rather than the access token itself, since URLs can leak via browser history or server logs. YNAB&amp;rsquo;s backend then exchanges that code for an access token over an authenticated HTTPS &lt;code&gt;POST&lt;/code&gt; request that includes its &lt;code&gt;client_secret&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The guide introduces the standard terminology (&lt;code&gt;resource owner&lt;/code&gt;, &lt;code&gt;OAuth client&lt;/code&gt;, &lt;code&gt;authorization server&lt;/code&gt;, &lt;code&gt;resource server&lt;/code&gt;, &lt;code&gt;scope&lt;/code&gt;) alongside the developer&amp;rsquo;s perspective: registering the app to obtain a client ID and client secret, and whitelisting a &lt;code&gt;redirect_uri&lt;/code&gt; so the authorization server refuses to redirect users to malicious domains. The author contrasts the front-channel (passing through the user&amp;rsquo;s browser via URL parameters visible to anyone along the path) with the back-channel (direct server-to-server calls via &lt;code&gt;POST&lt;/code&gt; bodies), and explains why single-page and mobile apps—which cannot keep a &lt;code&gt;client_secret&lt;/code&gt; confidential—use PKCE instead, a mechanism now recommended even for backend web apps. The post wraps up with a quick tour of the legacy implicit flow, refresh tokens, and OpenID Connect, the identity layer built on top of OAuth that powers &amp;ldquo;Sign in with Google.&amp;rdquo; As the author sums up, OAuth feels complex because every step was added to close a specific attack vector.&lt;/p&gt;
&lt;h2 id="professional-development-is-a-choice"&gt;&lt;a href="https://alexchesser.medium.com/professional-development-is-a-choice-e90fb8719259" rel="noopener noreferrer"&gt;Professional Development Is a Choice&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Alex Chesser, a developer with over 20 years of experience, argues that intentional professional development is very different from the passive growth that happens through day-to-day work: it requires a conscious choice. Looking back on his own career—maintaining Perl scripts at Nortel, getting laid off in the dot-com crash, spending five years teaching, and eventually returning to software engineering—he admits that for most of his career he learned reactively, picking up only what was needed for the task right in front of him. He also points out why top-down corporate career-development frameworks usually fail: the power imbalance between managers and direct reports makes it risky for employees to be completely honest about what they actually want.&lt;/p&gt;
&lt;p&gt;He proposes a four-step personal framework. First, put a recurring one-hour &amp;ldquo;career retrospective&amp;rdquo; on your calendar every week. Second, work through structured reflection questions—what you&amp;rsquo;re good at, what you enjoy, what the market pays you for, where you need to improve, and where you want to be in 1–3, 3–5, and 5–10 years—and turn the answers into SMART goals, making sure to include health, family, and non-work passions so you don&amp;rsquo;t burn out. Third, protect focused execution blocks using deep work or Pomodoro techniques, and fourth, revisit the loop weekly to adjust your targets. The author stresses that choosing not to invest extra time in career growth is also a completely valid choice—as long as you make it consciously.&lt;/p&gt;
&lt;h2 id="replacing-a-cache-service-with-a-database"&gt;&lt;a href="https://avi.im/blag/2025/db-cache/" rel="noopener noreferrer"&gt;Replacing a cache service with a database&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Avi asks a provocative question: can a database completely replace a dedicated caching service? Caches solve a vital problem—serving precomputed data at sub-millisecond latency—typically using the cache-aside pattern, where the application talks to both the cache and the database and takes responsibility for keeping them in sync. To simplify the architecture, you might try using a read replica as a cache: databases already keep hot pages in memory via their buffer pool, and if the application can tolerate replication lag, an asynchronous read replica can serve reads using the exact same SQL queries while eliminating custom cache-invalidation code. Embedded read replicas go further by avoiding network round-trips altogether, though synchronization still requires dedicated tooling (Litestream, for example, continuously streams SQLite backups to object storage rather than maintaining a live queryable replica out of the box).&lt;/p&gt;
&lt;p&gt;Still, dedicated caches hold major advantages: spinning them up or tearing them down is cheap, developers control exactly which keys are stored, caches can hold precomputed results of expensive multi-table joins, they natively support per-key TTLs and eviction policies, they don&amp;rsquo;t require replicating terabytes of cold data just to serve a few gigabytes of hot keys, and they effortlessly handle hundreds of thousands of concurrent connections whereas database connections are resource-heavy. To close the gap, the author argues databases would need partial read replicas, support for massive numbers of lightweight replicas, and built-in Incremental View Maintenance (IVM) to keep query results precomputed the way Noria (now ReadySet) does. His conclusion: we aren&amp;rsquo;t there yet.&lt;/p&gt;
&lt;h2 id="bonus-cool-diagrams-from-bytebytego"&gt;Bonus: Cool diagrams from &lt;a href="https://bytebytego.com/" rel="noopener noreferrer"&gt;ByteByteGo&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;&lt;img src="https://substack-post-media.s3.amazonaws.com/public/images/f8993d4d-8879-4eeb-9635-3a5aa13816cc_2250x2624.png" alt="A Detailed Guide to Content Delivery Networks"&gt;
&lt;img src="https://substack-post-media.s3.amazonaws.com/public/images/607358c5-2e0b-41fc-9cdd-a350e1faf144_3780x4096.jpeg" alt="CI/CD Pipeline Explained"&gt;
&lt;img src="https://substack-post-media.s3.amazonaws.com/public/images/8b1bd4d5-a708-4793-a9e6-aa96db182f54_3000x3900.png" alt="What are some of the most popular versioning strategies?"&gt;
&lt;img src="https://substack-post-media.s3.amazonaws.com/public/images/c34a8b8b-feff-4473-9eb1-dd399f5a81eb_2360x2664.jpeg" alt="The Testing Pyramid"&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Overall, I think this experiment went pretty well. The summaries are still a bit wordy and there were a few minor phrasing hiccups in Vietnamese, though for the price of free, it&amp;rsquo;s more than good enough :))) See you in upcoming posts!&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;This post was rewritten by Claude Code with Opus 5.5 on 27/09/2026; reviewed and edited by Codex with GPT 6.1 Sol on 09/11/2026, and re-verified by Claude Code with Sonnet 5.5 on 16/11/2026.&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>