Forem: Vaibhav

Port vs Backstage - Choosing Your Internal Developer Portal

Vaibhav — Thu, 21 Dec 2023 12:15:06 +0000

Internal developer portals (IDPs) are becoming increasingly popular as organizations strive to improve their developer experience. Developer platforms serve as access points to a more organized development environment, where developers can access tools, share knowledge, and collaborate to create better software faster.

Two of the most popular internal developer portals are Backstage and Port. Both platforms offer a wide range of features, but they have different fortes and shortcomings. This blog post is a detailed comparison of Port vs Backstage, what they're good at, and where they might fall short.

So, if you're deciding which internal developer portal is right for your team or organization, you are at the right place. Let's understand Backstage and Port to find the insights that will guide your decision and help you optimize your software development process. Before we delve into the specifics, let's get familiarised with the basics of Backstage and Port.

What is Backstage?

Backstage is an open source IDP developed by Spotify that has gained significant popularity in the software development community. Backstage offers a holistic solution for managing services, infrastructure, documentation, and more, all within a single platform. To understand it better, you can check out our Backstage blog post, where we have discussed it in detail.

What is Port?

Port is a SaaS-based IDP that is designed to be easy to use and get started with. It offers a set of pre-built features and integrations that can be used to create a functional IDP quickly. To know more about Port, you can read our Port blog post.

Comparing Backstage and Port

Since both Backstage and Port are designed to serve as internal developer portals, they share more similarities than differences. Let’s discuss some of their most common features before we move on to their respective strengths and challenges.

Common features

Service catalog: Both Backstage and Port provide a catalog for organizing and discovering internal services.
Plugin architecture: Both platforms support a plugin architecture, allowing for extensibility and customization.
CI/CD integration: Both integrate with CI/CD systems, enabling automation of the development lifecycle.
Documentation: Both platforms offer documentation features, enabling the creation and management of comprehensive documentation for services, APIs, and other resources.
Collaboration: Both Backstage and Port include collaboration tools to facilitate teamwork, knowledge sharing, and contributions to the development process.
Security: Both platforms likely include security features to manage and enforce security policies for services and APIs.
Tech stack agnostic: Both are designed to be agnostic to the underlying technology stack, accommodating various programming languages and frameworks.

Now, let's explore the unique strengths and challenges of each IDP.

Strengths of Backstage

Open source with great community support: Being open source, Backstage benefits from a vibrant community that continually contributes to its development. This support ensures that the platform stays up-to-date and relevant.
Extensive plugin ecosystem: Backstage boasts an impressive plugin ecosystem, allowing you to extend and customize the platform to suit your organization's specific needs. Whether it's a custom integration or a specialized tool, you'll likely find a plugin to meet your requirements.
Scalability: Backstage is often considered more scalable than other IDPs due to its modular architecture, extensive plugin ecosystem, and active community support. Backstage's open-source nature and backing by Spotify contribute to its scalability, allowing developers to easily customize and extend the platform to meet diverse needs, fostering adaptability and growth in various environments.
Choice of deployment: You can deploy Backstage on-premise or in the cloud, giving you control over where your data resides and making it suitable for organizations with diverse infrastructure requirements and various compliance requirements.

Challenges with Backstage

Steep learning curve: Backstage's extensive features and customization options come at a cost—a steep learning curve. Becoming proficient with the platform may require time and effort, especially for teams that are less technically experienced. Below is the screenshot from the Reddit post:
Resource-intensive setup and management: Setting up and managing Backstage can be resource-intensive, requiring dedicated technical expertise. This could be a challenge for smaller organizations or teams with limited resources.
Below is the screenshot of the Reddit post:

Strengths of Port

User-friendly interface: Port is known for its intuitive and user-friendly interface, making it accessible to a wide range of users, including those with limited technical expertise.
Quick setup/smooth learning curve: Port is designed for rapid deployment, allowing organizations to start quickly. Its simplified approach reduces the learning curve, making it an ideal choice for teams seeking a hassle-free setup.
Wide range of pre-built features: Port has a comprehensive set of pre-built features, reducing the need for extensive customization. This can be advantageous for organizations looking for out-of-the-box solutions.

Challenges with Port

Limited extensibility/customization: Compared to Backstage, Port has limited extensibility and customization options. It operates on a "no coding required" model, which may not cater to organizations with highly specialized needs. Though Port offers an open-source solution called Ocean for extensibility, it requires knowledge of Python and Ocean framework to make customizations.
Commercial product with a paid subscription: Port is a commercial product, and a paid subscription is required for organizations with more than 15 developers working on a project. For organizations looking to try out the product or have a small team consisting of 15 or fewer developers, Port is free.
Only SaaS offerings, no on-premise deployment: Port offers only SaaS (Software as a Service) deployments, so you won't have the option to host it on-premise or on your cloud infrastructure.

Navigating the UI

You can explore the user interfaces of Backstage and Port through their interactive demo projects, understanding the platforms' look and feel. Navigate through the demos to gain firsthand experience of each tool's functionalities, which can help you make an informed decision about the one that best suits your development needs.

Below are the screenshots of the Backstage and Port’s Home Page after logging in.

Backstage’s Home Page UI

Port’s Home Page UI

Here is a table that summarizes the key differences between Backstage and Port.

Feature/Platform	Backstage	Port
Open source	Yes	No
SaaS-based	No	Yes
Resource intensive	Highly resource intensive	Less resource intensive
Extensibility	Highly extensible using Plugins	Less extensible
Ease of use/Learning curve	More complex to set up and configure	Easier to set up and configure
Pre-built features	Less extensive set of pre-built features	More extensive set of pre-built features

Choosing the right platform

Now that we've explored the strengths and challenges of Backstage and Port, it's essential to make an informed choice based on your organization's unique needs, so you don’t fail at platform engineering. Below are the points that can help you with that.

Backstage is a good choice for:

Organizations with diverse tools and processes: Backstage’s extensive plugin ecosystem and customization capabilities make it an ideal choice for organizations dealing with a multitude of services, intricate workflows, and diverse tech stacks. The ability to tailor Backstage to meet specific organizational needs ensures that large enterprises can efficiently manage their complex development lifecycles.
Organizations with a dedicated team of developers with required technical expertise: Given its robust feature set and customization options, Backstage is best managed by a team of skilled developers. Organizations that often have the resources and technical expertise required to navigate the complexities of Backstage can integrate it seamlessly into their existing workflows.
Organizations that need on-premise deployment due to compliance requirements: Some industries or organizations necessitate on-premise deployment of their developer portals due to regulatory or compliance requirements. Backstage offers the flexibility to be deployed on-premise, providing organizations with control over their infrastructure and data. This becomes crucial for enterprises that must adhere to strict compliance standards and data security protocols, ensuring that sensitive information is kept within the organization's premises.

Port is a good choice for:

Organizations looking for a user-friendly IDP: Port offers a straightforward and user-friendly IDP. Its intuitive interface simplifies the onboarding process, allowing even non-technical users to navigate and leverage the platform efficiently. This simplicity ensures that organizations can quickly adapt to Port without extensive training.
Organizations with resource constraints: Port doesn't require an extensive technical skill set for management. This makes it an attractive choice for organizations with limited resources allowing them to benefit from a developer portal without the need for a specialized team to manage it.

Note: If both Port and Backstage are not suitable for your project, you can begin platform engineering with Kratix, or get a custom built.

Conclusion

Backstage and Port both offer valuable solutions for platform engineering needs, the choice between them depends on the specific characteristics and requirements of your organization. Backstage excels in complex, large-scale environments where customization and technical expertise are paramount. Port, however, is tailored for organizations seeking a user-friendly and hassle-free IDP that doesn't demand extensive technical skills.

Carefully evaluating your organization's size, development processes, and technical capabilities will help you choose the IDP that aligns best with your organization’s unique needs and goals. To explore further and receive personalized recommendations for your IDP, get in touch with our platform engineering consulting team and talk to our experts. Making an informed decision will pave the way for a more efficient and streamlined development process within your organization. Also, feel free to share your thoughts with me on the blog post. Connect with me on LinkedIn.

Exploring Platform Engineering? Read the other blogs from our Platform Engineering series:

Building a Platform? Download our free Platform Engineering OSS Reference Architecture eBook!

Starting Platform Engineering Journey with Backstage

Vaibhav — Wed, 18 Oct 2023 04:56:06 +0000

In the continuously growing landscape of platform engineering, which emerged from the DevOps practices to provide self-service capabilities for software development teams, internal developer portals or IDPs are playing an increasingly important role. By improving collaboration and increasing visibility and control, internal developer portals are helping organizations deliver quality software quickly and efficiently.

One of the popular tools out of the many different internal developer portals on the market is Backstage. Backstage aims to enhance the developer experience significantly by providing a central place for developers to discover and use services. This blog post explores its key features and benefits, revealing how it helps in the development process. But first, let's briefly understand what internal developer portals are and why they are crucial in the software industry.

What is an internal developer portal (IDP)?

An internal developer portal is a website or web application that provides information and tools to developers who are building applications on top of a company's platform. Platform engineering focuses on empowering developers to build and deploy software quickly and efficiently. Internal developer portals are essential tools for achieving platform engineering goals. They provide a single point of entry for developers to access all of the resources they need, including APIs, documentation, tools, and services.

The need for internal developer portals in the software industry

Development teams usually face challenges in the traditional software development process like lack of documentation, navigating to multiple dashboards for various sets of requirements etc., making it difficult to understand and implement technologies. The lack of a centralized tool leads to confusion, increased development time, and a higher likelihood of errors. Internal developer portals streamline this process, providing a centralized place for documentation, API details, and tools. They bridge the gap between developers and technology, reducing friction and enhancing overall efficiency in the software development process.

Internal developer portals have become a necessity for several reasons:

Streamlined accessibility: As the number of APIs and services increases, developers require a central place that aggregates these resources, making them easily accessible and searchable. Internal developer portals serve as a one-stop destination where developers can explore and select the right tools for their projects.
Effective documentation: Clear and concise documentation is very important for seamless API integration & product development. An internal developer portal hosts comprehensive guides, tutorials, and examples that assist developers in understanding the functionalities, methods, and best practices associated with each API.
Enhanced collaboration: Developers often work in teams or in collaboration with others, where effective communication and sharing of knowledge is important. Internal developer portals foster a sense of community where developers can share experiences, seek advice, and collaborate on solving challenges.
Accelerated development: The integration of pre-built code samples and SDKs into internal developer portals quickens the development process. Developers can utilize these boilerplate resources to jumpstart their projects, saving valuable time and effort.

There are a number of other internal developer portals available on the market, such as Port, Kratix, and Cortex. These portals offer a variety of features, such as software catalogs, documentation management, and user management. However, in this blog post, we will focus on Backstage, an open-source internal developer portal platform that is used by companies like Spotify and Netflix.

What is Backstage?

Backstage is an open source platform developed by Spotify and subsequently donated to the Cloud Native Computing Foundation (CNCF) in 2020. It aims to serve as an "internal developer portal" and streamline the developer experience by providing a unified and centralized platform to manage all aspects of the software development lifecycle.

Key components of Backstage

Some of the key components of Backstage are:

Software Catalog

The Software Catalog is one of the foundational features of Backstage. It acts as a centralized repository that provides a comprehensive overview of all the services, APIs, and components within an organization's software ecosystem. Each service entry in the catalog includes essential information such as its purpose, owner, documentation, dependencies, and health metrics.

Software templates

Backstage offers software templates that expedite the process of creating new services and projects. These templates provide standardized starting points for various types of applications, ensuring consistent best practices, coding conventions, and integrations from the very beginning. This feature not only accelerates development but also enforces consistency across projects, leading to higher-quality codebases.

CI/CD integration

Continuous Integration and Continuous Delivery (CI/CD) are vital practices in modern software development. Backstage seamlessly integrates with CI/CD pipelines, allowing developers to trigger builds, run tests, and deploy code directly from the platform. This integration streamlines the development workflow, reduces manual intervention, and enhances the speed and reliability of delivering software updates.

Documentation management

Efficient documentation management is crucial for effective software development. Backstage offers tools to manage, version, and publish documentation related to services and APIs. This ensures that developers always have access to up-to-date and relevant documentation, minimizing confusion and promoting accurate implementation.

Analytics and metrics

Understanding how services are performing is essential for maintaining a healthy software ecosystem. Backstage can be extended to include analytics and metrics related to service health, performance, and usage. This data empowers teams to make informed decisions, optimize resource allocation, and proactively address issues.

Benefits of Backstage

Some of the key advantages of using Backstage are:

Open source: Backstage is an open-source project, which means that it is free to use and modify. This gives organizations more flexibility and control over their internal developer portals.
Extensibility: Backstage is highly extensible owing to its huge plugin ecosystem, which means that it can be easily integrated with other tools and services that organizations are already using. This can help to reduce silos and create a more seamless developer experience.
Community support: Backstage has a large and active community of users and contributors. This means that there is a wealth of information and support available online.
Enhanced collaboration: By providing a centralized platform, Backstage encourages better collaboration among developers, infrastructure teams, and other stakeholders. It brings different teams together, fostering a sense of community and shared responsibility.
Improved developer productivity: Backstage simplifies the developer experience by offering a unified interface for various tools and resources. Developers spend less time searching for information and more time coding, ultimately increasing their productivity.
Consistent development practices: With Backstage, teams can enforce standardized development practices across projects. This consistency ensures code quality, security, and compliance, leading to more robust and reliable software.
Efficient onboarding: Onboarding new team members can be challenging, but Backstage streamlines this by providing clear and accessible documentation. Newcomers can quickly grasp project essentials and start contributing effectively.

Getting Started With Backstage

The official Backstage documentation is the best resource for getting started with Backstage. It is comprehensive, up-to-date, and easy to follow. The documentation covers everything from installing and configuring Backstage to creating and managing software components. It also includes tutorials and examples to help you get started quickly.

Backstage can be installed and run on a local or remote server as a standalone application and you can customise and build portals on top of it using its extensive plugin ecosystem to cater for the needs of your development teams. We will install a backstage application in the following section.

Installation steps for Backstage

Pre-requisites

Before starting with Backstage, let's ensure to have the essential prerequisites in place to guarantee a smooth installation process. Here is the list of tools we would need to get started:

Unix-based Operating System (Linux, macOS, WSL)
NodeJs with NVM
Yarn
Git
System binaries like curl or wget

Installing Backstage App

We use npx, a tool that runs Node executables directly from the registry, to install the Backstage Standalone app. This tool is included with the Node.js installation. The following command will install Backstage:

npx @backstage/create-app@latest

The wizard will ask for the name of the app, which will also be the name of the directory

Need to install the following packages:
  @backstage/create-app@0.5.5
Ok to proceed? (y) y
? Enter a name for the app [required] backstage-blog

Running Backstage App

Once the installation is completed, a directory will be created with the app name that was chosen during installation. Migrate to the directory and start the Backstage application.

cd backstage-blog
yarn dev

The Backstage application will start on port 3000. Migrate to the local browser and type http://localhost:3000 to open the Backstage application.

Backstage Software Catalog

Backstage’s Software Catalog is built around the concept of metadata YAML files stored together with the code, which are then harvested and visualized in Backstage. Let’s understand how we can import services into our catalog and visualize relationships between them.

Creating config.yaml

To import any service into the Software Catalog let’s create a config.yaml file in the root directory of your GitHub repository which looks like this:

apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
  name: boutique-carts
  annotations:
    github.com/project-slug: infracloudio/backstage-msvc-app/src/cartservice     
spec:
  type: service
  lifecycle: production
  owner: user:guest
  dependsOn:
    - component:boutique-frontend
    - component:boutique-products
  providesApis:
    - boutique-carts-api

The above config.yaml corresponds to boutique-carts service located at the following Github location: infracloudio/backstage-msvc-app/src/cartservice
The dependsOn and providesApi specification helps to visualize the relationship between various services. All the components mentioned here can be created similarly to boutique-carts service.

Importing config.yaml into Software Catalog

Open Backstage UI in the browser, Go to Home and Select Create.
Select Register existing components.
Add the absolute path to the service’s config.yaml file. Select Analyze and Import it into catalog.

Navigating service inside the Software Catalog

Options that are available under the Overview tab
CI/CD tab automatically imports all Github Actions workflows from the imported repository
API and Dependencies can be visualized under their separate tabs

To sum it up, in the short demo above, we learned how to add services to our catalog and visualize their relationships. This helps in creating an efficient and user-friendly catalog. You can explore many other use cases using Backstage to suit the needs of your developers.

Conclusion

In conclusion, the evolution of technology and the increasing demand for interconnected digital services have highlighted the critical need for internal developer portals. In this landscape, Backstage offers a comprehensive solution that not only meets the requirements of modern software development but also provides a lot of advantages.

Backstage's unique blend of simplified developer experiences and an extensive array of components and tools places it at the forefront of the internal developer portal ecosystem. It empowers developers with clear documentation, APIs, and self-service capabilities, reducing friction and accelerating innovation.

As organizations continue to adapt and expand in the digital world, having a powerful and versatile internal developer portal like Backstage is no longer a luxury but a necessity. Connect with our platform engineering consulting team to kickstart your journey with Backstage which can enable your development teams to collaborate better and deliver efficiently.
Also, feel free to share your thoughts with me on the blog post. Connect with me on LinkedIn.