Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Serverless ETL and Analytics with AWS Glue

You're reading from  Serverless ETL and Analytics with AWS Glue

Product type Book
Published in Aug 2022
Publisher Packt
ISBN-13 9781800564985
Pages 434 pages
Edition 1st Edition
Languages
Authors (6):
Vishal Pathak Vishal Pathak
Profile icon Vishal Pathak
Subramanya Vajiraya Subramanya Vajiraya
Profile icon Subramanya Vajiraya
Noritaka Sekiyama Noritaka Sekiyama
Profile icon Noritaka Sekiyama
Tomohiro Tanaka Tomohiro Tanaka
Profile icon Tomohiro Tanaka
Albert Quiroga Albert Quiroga
Profile icon Albert Quiroga
Ishan Gaur Ishan Gaur
Profile icon Ishan Gaur
View More author details

Table of Contents (20) Chapters

Preface 1. Section 1 – Introduction, Concepts, and the Basics of AWS Glue
2. Chapter 1: Data Management – Introduction and Concepts 3. Chapter 2: Introduction to Important AWS Glue Features 4. Chapter 3: Data Ingestion 5. Section 2 – Data Preparation, Management, and Security
6. Chapter 4: Data Preparation 7. Chapter 5: Data Layouts 8. Chapter 6: Data Management 9. Chapter 7: Metadata Management 10. Chapter 8: Data Security 11. Chapter 9: Data Sharing 12. Chapter 10: Data Pipeline Management 13. Section 3 – Tuning, Monitoring, Data Lake Common Scenarios, and Interesting Edge Cases
14. Chapter 11: Monitoring 15. Chapter 12: Tuning, Debugging, and Troubleshooting 16. Chapter 13: Data Analysis 17. Chapter 14: Machine Learning Integration 18. Chapter 15: Architecting Data Lakes for Real-World Scenarios and Edge Cases 19. Other Books You May Enjoy

Defining an SLA for a data platform

When operating a data platform, it is essential to define a healthy state for the entire data platform and maintain that state. Think about what kind of state the data platform should be in. It would be good to define an SLA as an indicator of health. This SLA does not always need to be communicated to end users but is used as an internal indicator to measure whether your data platform is healthy or not.

The basic strategy is to maintain a certain data platform state where the SLA is met and then recover to the normal state when it fails. In other words, monitoring is performed to understand when the platform has deviated from a normal state to an abnormal state, and recovery is performed to return the data platform from an abnormal state to a normal state, as illustrated in the following diagram:

Figure 11.1 – The monitoring cycle

Now, I would like to look at an example of how to define the health of a data platform...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}