Scalability & Delivery
Overview
A faster listing page is useful when it still returns the required records and enforces permissions. This part examines how to measure that work, reduce its cost and release a verified change.
We will define a successful read and compare repeated measurements. Then we will inspect database plans, reduce repeated queries and calculate a connection budget across API instances. Finally, we will run automated checks and consider what happens when a new API meets an older browser client.
The examples build on the common core’s requests, transactions and tests. They introduce CI and run locally. Each programming exercise supplies its own starting code, so you can concentrate on the operation being studied.
Part structure
- Measuring Performance & Load: define successful work and interpret latency, throughput and errors.
- Database Performance: read plans and evaluate an access-pattern index.
- Resource Limits: budget connections and distinguish shared state from local controls.
- Continuous Integration: follow a change through repeatable checks and diagnose a failed run.
- Continuous Delivery & Operations: follow an identified release while preserving older consumers.
- Recap and Feedback: reflect on the part and give feedback.