Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying The Platform Engineer's Handbook
  • Table Of Contents Toc
The Platform Engineer's Handbook

The Platform Engineer's Handbook

By : Ajay Chankramath
close
close
The Platform Engineer's Handbook

The Platform Engineer's Handbook

By: Ajay Chankramath

Overview of this book

The Platform Engineer’s Handbook equips senior engineers and DevOps professionals to deliver developer-friendly infrastructure with automation, speed, AI acceleration, and intelligence. Starting with a blank slate, you’ll build a complete, modern platform that runs locally on your laptop, learning real-world patterns as you go. In this handbook, you’ll follow a structured, progressive journey, beginning with source control governance and branching strategies, then deploying a Kubernetes-based runtime, embedding observability, and securing platform access. You’ll implement self-service onboarding, CI/CD as a service, and developer portals with Backstage. Later chapters introduce infrastructure blueprints, policy as code, FinOps observability, and AI-augmented platform services such as agent-based onboarding and copilots for pipeline creation. Each chapter combines core concepts, lab-based exercises, and production-ready best practices to provide a comprehensive understanding of the subject matter. By the end, you'll have a working MVP platform and the skills to adapt and scale it for your team or organization.
Table of Contents (21 chapters)
close
close
Lock Free Chapter
1
Part 1: Designing, Building, and Deploying the Core Engineering Platform
7
Part 2: Enhancing Productivity Through Self-Service Functions
13
Part 3: Scaling, Maturing, and Evolving Your Platform
20
Index

Ensuring Commit Conventions

Once the repository setup decisions are made, you need to start looking into the specific conventions you will use for committing the code. Start by defining the structure of the commits (say, what information is required in a commit message) and then include the types of commits—whether they are a new feature, bug fix, documentation, refactoring, test-related, and so on. Also, tag the commits to make sure you can easily find those commits later, irrespective of the tracking tool you are using. One benefit is the idea of setting up pre-commit hooks to validate the commit message. You should use any tools you are already using for interactive activities around it, as well as linting and running quick tests to validate them. The more developers contributing to the platform code, the more you can make hooks a mandatory part of their workflow.

Commit conventions and policy automation aren't just rules for the sake of rules — they...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
The Platform Engineer's Handbook
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon