Recap and Feedback
Performance comparisons require successful work under comparable conditions. Query plans help explain database work, and joins can reduce repeated queries while preserving the required records and fields. Several API instances share one database connection budget while keeping their own process-local controls.
A failed pipeline stage must remain a failure after cleanup. A running release must also pass checks of its intended request paths and remain compatible with supported older consumers and existing data. Source checks, HTTP requests and browser checks provide evidence for different parts of that behavior.
Choose one observation you can now explain and one question that remains open. Revisit the relevant query plan, run summary or release example as needed, then use the feedback form to describe what helped and where you needed more support.
Reflection and feedback
0 / 5 points
Reflect on the material and exercises in this part. For the agreement statements, 1 means strongly disagree and 7 means strongly agree. Your feedback helps improve the course.