Building a state-of-the-art development platform with Backstage

The recent InfoWorld article, "Building a state-of-the-art development platform with Backstage," delves into the nuanced role of Backstage within modern internal developer platforms. It begins by acknowledging Backstage's widespread adoption as the go-to solution for developer portals, effectively solving the "discovery problem" that previously plagued organizations with disparate wikis, spreadsheets, and tribal knowledge. Backstage's unified catalog, rich plugin ecosystem, and golden-path templates have been instrumental in bringing structure and consistency to how developers find and provision services. However, the article makes a crucial distinction: Backstage serves as a portal, not a complete platform. A portal, it explains, is primarily concerned with organizing information, documentation, and templates. In contrast, a true development platform encompasses the execution layer, handling critical aspects like deployments, environment management, policy enforcement, observability, and runtime operations. The real complexity, the author argues, resides in this underlying execution layer, which Backstage assumes to exist beneath it. The piece highlights a common challenge: many organizations, after deploying Backstage, realize that point-to-point integrations between Backstage and various CI/CD, GitOps, Kubernetes, and observability tools can become a significant maintenance burden, leading to a "messy middle" of fragile custom wiring. To overcome this, the article advocates for a product mindset in platform design, starting with understanding developer pain points and designing a coherent system to address them. A key recommendation is the strategic use of abstractions. While developers interact with high-level concepts like components and endpoints, the platform itself requires its own set of abstractions to define standards, enforce policies, and create structure without requiring low-level configurations for every scenario. This approach allows the platform to translate developer-friendly declarations into concrete infrastructure configurations, such as Kubernetes namespaces and network policies, ensuring consistent and compliant deployments. The article emphasizes that these abstractions should not just be static representations but should also have associated runtime semantics, reflecting actual permitted traffic flow and dependency management. Ultimately, the article asserts that while Backstage is an indispensable component for any internal developer platform, especially for its ability to streamline developer experience and foster adoption, it must be complemented by a well-designed and robust execution layer. This integrated approach allows organizations to leverage Backstage's strengths while building a truly state-of-the-art development platform that reduces cognitive load for developers and enforces organizational best practices.