PlayCloudLabs
Sign in
  1. Learn AWS
  2. Architecture
  3. Cache-aside reads

Architecture pattern

AWS Cache-aside reads architecture

when reads vastly outnumber writes and the database feels it

The application asks the cache first and falls back to the database on a miss, writing the answer back as it goes. Most reads never reach the database, which is what lets a modest instance serve a large audience.

What it runs through

In the order a request or a record moves through it. Each one links to the page that explains it.

Signals in a brief that point here

Phrases that, when you meet them in a scenario, mean this shape rather than another. They are the tell, and they are what an exam question is built around.

  • “read heavy”
  • “a hundred times more reads than writes”
  • “the same data over and over”
  • “database under load”

What it costs you

Two copies of the truth. Every write needs a story for how the cache stops being wrong.

Every shape has one. A design decision with no stated downside is usually a decision nobody has finished making.

Learn the services in it

Shapes it is easily confused with

These run through some of the same services, which is exactly why a brief that fits one can look like it fits another.

Now build it from a brief

Reading a shape and producing one from a scenario that never names a service are different skills, and the exam asks for the second. The scenarios give you the brief; you draw the architecture and it is scored against what the brief requires.

Still there?

You have been away for a while. We have saved what you were working on in this browser. In 60 seconds you will be signed out to keep your account safe.