Menu

Module 10

🚀

Performance & Scalability Patterns

Patterns that make systems fast and scalable: cache-aside, write-behind, index tables, claim check, and pipes-and-filters processing.

9 lessons~104 min

What you'll learn

  • Implement the Cache-Aside pattern for read-heavy workloads
  • Design write-through and write-behind caching for write optimization
  • Use index tables and materialized views for query acceleration
  • Apply the Claim Check pattern to reduce message payload sizes
  • Build processing pipelines with the Pipes and Filters pattern
1

Cache-Aside Pattern

Load data into cache on demand: the cache-aside flow, cache miss handling, consistency considerations, and stampede prevention.

12m
High
2

Write-Through & Write-Behind Caching

Synchronous vs asynchronous cache writes: write-through for consistency, write-behind (write-back) for performance, and their failure modes.

12m
High
3

CQRS Read Models for Performance

Optimize reads independently from writes: denormalized read stores, projection patterns, and keeping read models eventually consistent.

12m
High
4

Sharding as a Scalability Pattern

Horizontal data partitioning for write scalability: shard key strategies, range vs hash sharding, cross-shard queries, and rebalancing.

15m
High
5

Index Table Pattern

Create secondary indexes as separate tables: enabling efficient queries on non-primary-key fields in NoSQL and sharded databases.

10m
Medium
6

Static Content Hosting Pattern

Serve static assets directly from object storage and CDNs: reducing server load, cache headers, versioned deployments, and edge computing.

8m
Medium
7

Claim Check Pattern

Reduce message size by storing large payloads externally: the claim check flow, storage backends, and maintaining message processing efficiency.

8m
Medium
8

Pipes and Filters Pattern

Decompose processing into a pipeline of independent filters: composability, parallel execution, error handling, and real-world data pipeline examples.

12m
Medium
9

Choreography vs Orchestration

Two models for coordinating services: event-based choreography (decentralized) vs command-based orchestration (centralized). Trade-offs and when to use each.

15m
High