Summary
In this chapter, you learned why we need observability to fail forward fast and how serverless makes it easier to collect useful metrics. You also learned how to leverage FinOps and cost metrics to help decide when it is worth tuning our services.
We dug into the details, and you learned how to use resources metrics and the USE method, and work metrics and the RED method, to turn observability data into actionable information. You learned how to monitor the frontend with real user monitoring and synthetics. You also learned about continuous performance tuning and reviewed some common tuning tips.
In the next and final chapter, we will round out our discussion on architecting for innovation, with thoughts on getting started, gaining trust, and building momentum. We will address some of the myths and anti-patterns that keep teams from getting off the ground and cover the various hurdles and impediments that teams must confront.
Leave a review!
Enjoying this book...