Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
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

Taking technical debts consciously

Choose your technical debt wisely,” your author, Hilliary, says all the time. But what does it mean to choose your technical debt? Aren’t we supposed to be solving problems and identifying solutions?

Yes. But these two things are not mutually exclusive. There’s not likely to be a perfect solution readymade off the shelf. Typically, products are designed with specific use cases in mind, but those use cases are not all-encompassing. No product can cover every permutation of every user’s potential needs and workflows. Indeed, it will be the same for your platform as you progress through its life cycle. When we commit to accepting the shortcomings of a solution or technology, that means we’re committing to compensating for that in another way. Such compensation should be managed so that we don’t create additional overhead or manual workflows that result in unsustainable toil for the platform team or...

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