paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 23 Packages Projects Releases Wiki Activity
Files
66daa47c6a1265e8ff052d9dbcf17f9bb0893650
backstage/docs/overview/roadmap.md
T
Patrik Oldsberg 0b2ad28532 microsite: new email
2020-11-16 11:00:19 +01:00

6.8 KiB
Raw Blame History

id, title, description
id title description
roadmap Project roadmap Roadmap of Backstage Project

Current status

Backstage is currently under rapid development. This means that you can expect APIs and features to evolve. It is also recommended that teams who adopt Backstage today upgrade their installation as new releases become available, as Backwards compatibility is not yet guaranteed.

Phases

We have divided the project into three high-level phases:

  • 🐣 Phase 1: Extensible frontend platform (Done ✅) - You will be able to easily create a single consistent UI layer for your internal infrastructure and tools. A set of reusable UX patterns and components help ensure a consistent experience between tools.

  • 🐢 Phase 2: Service Catalog (alpha released) - With a single catalog, Backstage makes it easy for a team to manage ten services — and makes it possible for your company to manage thousands of them.

  • 🐇 Phase 3: Ecosystem (ongoing, see Plugin Marketplace) - Everyone's infrastructure stack is different. By fostering a vibrant community of contributors we hope to provide an ecosystem of Open Source plugins/integrations that allows you to pick the tools that match your stack.

Detailed roadmap

If you have questions about the roadmap or want to provide feedback, we would love to hear from you! Please create an Issue, ping us on Discord or reach out directly at backstage-interest@spotify.com.

Want to help out? Awesome ❤️ Head over to CONTRIBUTING guidelines to get started.

Ongoing work 🚧

  • Plugins for managing micro services end-2-end Out of the box Backstage will ship with a set of plugins (Overview, CI, API and Docs) that will demonstrate how a user can manage a micro service and follow a change all the way out in production. Completing this work will make it much easier to see how a plugin can be built that integrates with the Backstage Service Catalog.

  • Users and teams Ownership is a central concept in Backstage. It should be easy to import your existing organizational data, such as users and groups/teams, into Backstage. A user the logs into Backstage should see software components owned by the team(s) they are in.

  • Backstage platform is stable - The platform APIs and features are stable and can be depended on for production use. After this plugins will require little to no maintenance.

  • Improved Kubernetes plugin - Native support for Kubernetes, making it easier for developers to see and manage their services running in k8s.
  • Further improvements to platform documentation. Examples include a Golden Path for plugin development.

Future work 🔮

  • Deploy a product demo at demo.backstage.io - Deploy a typical Backstage deployment available publicly so that people can click around and get a feel for the product without having to install anything.

  • Global search - Extend the basic search available in the Backstage Service Catalog with a global search experience. Long term this search solution should be extensible, making it possible for you add custom search results.

  • [TechDocs V.2] Stabilization release - Platform stability and compatibility improvements.

  • Additional auth providers - Backstage should work for most (all!) auth solutions. Since Backstage can be used by companies regardless of what cloud (or on prem) you are using we are especially keen to get auth support for AWS, Azure and others.

  • Initial GraphQL API - A GraphQL API will open up the rich metadata provided by Backstage in a single query. Plugins can easily query this API as well as extend the model where needed.

Plugins

Building and maintaining plugins is the work of the entire Backstage community.

A list of plugins that are in development is available here. We strongly recommend to upvote 👍 plugins you are interested in. This helps us and the community prioritize what plugins to build.

Are you missing a plugin for your favorite tool? Please suggest a new one. Chances are that someone will jump in and help build it.

Completed milestones ✅

Reference in New Issue View Git Blame Copy Permalink