Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Platform Engineering for Architects

You're reading from   Platform Engineering for Architects Crafting modern platforms as a product

Arrow left icon
Product type Paperback
Published in Oct 2024
Publisher Packt
ISBN-13 9781836203599
Length 374 pages
Edition 1st Edition
Arrow right icon
Authors (3):
Arrow left icon
Hilliary Lipsig Hilliary Lipsig
Author Profile Icon Hilliary Lipsig
Hilliary Lipsig
Max Körbächer Max Körbächer
Author Profile Icon Max Körbächer
Max Körbächer
Andreas Grabner Andreas Grabner
Author Profile Icon Andreas Grabner
Andreas Grabner
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Part 1 – An Introduction to Platform Engineering and Architecture FREE CHAPTER
2. Chapter 1: Platform Engineering and the Art of Crafting Platforms 3. Chapter 2: Understanding Platform Architecture to Build Platform as a Product 4. Chapter 3: Building the Foundation for Supporting Platform Capabilities 5. Part 2 – Designing and Crafting Platforms
6. Chapter 4: Architecting the Platform Core – Kubernetes as a Unified Layer 7. Chapter 5: Integration, Delivery, and Deployment – Automation is Ubiquitous 8. Chapter 6: Build for Developers and Their Self-Service 9. Part 3 – Platforms as a Product Best Practices
10. Chapter 7: Building Secure and Compliant Products 11. Chapter 8: Cost Management and Best Practices 12. Chapter 9: Choosing Technical Debt to Unbreak Platforms 13. Chapter 10: Crafting Platform Products for the Future 14. Index 15. Other Books You May Enjoy

Architectural considerations for observability in a platform

Self-service and cognitive load – we’ve already alluded to the importance of observability in these topics. Your platform cannot act in service to its users without observability prioritized. In other words, you should expect to watch and measure everything.

Observability comes in two flavors; the first is observability for the benefit of the platform team. This is the way the platform team will collect data and information to help build their reliability. Using the site reliability practices of SLOs, the platform team can measure customer satisfaction by setting SLOs for the platform and then creating observability in support of them.

The good news is that, in the Kubernetes world, this is easier because of objects and microservices. The bad news is that there are a lot more things to measure than ever before due to microservices, and it’s hard to know whether you’ve captured everything...

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 $19.99/month. Cancel anytime