Skip to content

Lesson 3 of 6

The building blocks of a platform

Add a components section by listing typical parts of a platform, such as application templates, deployment pipelines, and environment management.

4 minPlatform Engineering

After this lesson, you will be able to list the typical components of an internal developer platform and explain what each one does.

Application templates

A platform often starts with application templates. A template is a ready-made project that has the files, folders, and settings a team needs to start a new service. Instead of copying an old project and changing names by hand, a developer picks a template and the platform creates a new repository with the right structure, build files, and configuration.

Templates make it easier to follow company standards. For example, a template for a web service might include a health check endpoint, a Dockerfile, and a pipeline definition. The developer does not need to remember every detail. The template also reduces the chance of mistakes, such as missing a security setting or using an old version of a library.

A platform can offer several templates for different kinds of work: a backend service, a frontend app, a scheduled job, or a data pipeline. Each template is maintained by the platform team, so updates can be rolled out to all new projects at once.

Deployment pipelines

A deployment pipeline is the set of steps that takes code from a repository to a running environment. A typical pipeline builds the code, runs tests, creates a package or container image, and deploys it to a target environment.

Without a platform, each team often writes its own pipeline scripts. That leads to duplication and differences in how things are done. With a platform, the pipeline is defined once, usually as part of the application template. The developer only needs to provide a few values, such as the name of the service and the environment to deploy to.

Pipelines in a platform are often triggered automatically when a developer pushes code or merges a pull request. The platform shows the status of each run and keeps a history, so it is easy to see what was deployed and when.

Environment management

An environment is a place where an application runs, such as development, staging, or production. Managing environments means creating them, configuring them, and tearing them down when they are no longer needed.

A platform can provide self-service environments. A developer can request a new environment for testing a feature without waiting for an operations team. The platform provisions the necessary resources, such as a database and a message queue, and connects the application to them.

Environment management also includes keeping environments consistent. The platform can use the same configuration for every environment, with only small differences such as the database connection string. This reduces the 'works on my machine' problem, where code behaves differently in different places.

Other common components

Application templates, deployment pipelines, and environment management are the core, but platforms often include other parts:

  • A service catalogue that lists all running services and their owners.
  • Secret management for storing passwords, API keys, and certificates safely.
  • Observability tools that collect logs, metrics, and traces from all services.
  • A developer portal, often a web interface, where developers can find templates, request environments, and see the status of their deployments.

Not every platform has all of these components. The exact set depends on what the organisation needs. The important idea is that a platform brings these pieces together in one place, with a consistent way to use them.

Key takeaways

  • Application templates give developers a standard starting point for new services.
  • Deployment pipelines automate the steps from code to a running environment.
  • Environment management lets developers create and manage environments on their own.
  • Other components, such as a service catalogue and secret management, support the core parts.
  • A platform combines these components into one consistent experience.

Try it

Write a one-page description of the components you would include in an internal developer platform for a small team of five developers building web applications. For each component, write one or two sentences explaining what it does and why the team needs it. A good result will list at least four components, including application templates, deployment pipelines, and environment management, and will explain how each one helps the team deliver software faster and with fewer errors.

Official documentation

Ready to use this in a job?

Rolebound applies to matching roles for you.

Start now

Written with AI and checked automatically. Tools change, so a command may behave differently in the version you install. Spotted a mistake? Tell us.

    Cookies on Rolebound

    We use necessary cookies to sign you in and keep the site working — those cannot be turned off. We would also like to set analytics and advertising cookies so we can see which pages help people get interviews and which adverts brought them here. Nothing optional is set unless you say yes, and you can change your mind at any time from “Cookie settings” in the footer. Read our Privacy Policy.

    The building blocks of a platform | Understanding Internal Developer Platforms | Rolebound