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

Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter/X handles. Here is an example: “The directory path is nested within the chart, and the use of this directory called crds/ allows Helm to pause while the CRDs are added to a cluster before continuing with the chart execution.”

A block of code is set as follows:

apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
  name: crontabs.stable.example.com
spec:
  group: stable.example.com
  version: v1
  scope: Namespaced
  names:
    plural: crontabs
    singular: crontab
    kind: CronTab
    shortNames:
    - ct

Any command-line input or output is written as follows:

$ kubectl label nodes platform-worker2 reserved=reserved
node/platform-worker2 labeled

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “These platform logs should also, as much as possible, be clear of any Personally Identifiable Information (PII).”

Tips or important notes

Appear like this.

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