Amazon Aurora DSQL: The Definitive Guide

Chapter 3. DSQL Architecture for Practitioners

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 3rd chapter of the final book. The GitHub repo is active.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

You don’t need to understand DSQL’s internals to use it. You can create a cluster, connect to it, and start writing SQL without knowing anything about what happens beneath the surface. But if you want to understand why DSQL behaves the way it does—why transactions sometimes fail at commit, why read-only queries are so fast, why cross-region writes add latency but cross-region reads don’t—you need to understand the architecture. This will help you create new applications using DSQL or migrate the applications you have.

This chapter is about building that mental model. I’m not going to cover every implementation detail (AWS hasn’t published all of them, and many will change over time). Instead, we’ll focus on the architectural decisions that directly affect how you design schemas, write queries, and build applications. By the end, you’ll be able to predict DSQL’s behavior in situations the documentation doesn’t explicitly cover—and that’s the real value of understanding architecture. ...