DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Death by a Thousand YAMLs: Surviving Kubernetes Tool Sprawl
  • The Open Source Climate Stack: Essential GitHub Repos Powering the Decarbonization Movement
  • Automatic Code Transformation With OpenRewrite
  • Internal Developer Portals: Modern DevOps's Missing Piece

Trending

  • When Snowflake Lies to You: Understanding False Failures in dbt Pipelines
  • Using LLMs to Automate Data Cleaning and Transformation Pipelines
  • Offline-First Patch Management for 10,000 Edge Nodes: A Practical Architecture That Scales
  • Exactly-Once Processing: Myth vs Reality
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. DevOps and CI/CD
  4. When Backstage Met Terraform: Exploring Platform Abstractions [Video]

When Backstage Met Terraform: Exploring Platform Abstractions [Video]

Discover key learnings from a fireside chat about the interactions between internal developer portals, platforms, and infrastructure as code.

By 
Daniel Bryant user avatar
Daniel Bryant
·
Aug. 23, 24 · Interview
Likes (2)
Comment
Save
Tweet
Share
6.0K Views

Join the DZone community and get the full member experience.

Join For Free

In a recent fireside chat, I delved into the intriguing convergence of Terraform and Backstage, two pivotal technologies reshaping the landscape of platform engineering. This session was particularly exciting as I had a special guest, Seve Kim, a product manager from Backstage, joining Abby Bangser and me! 

Although the chat only lasted 30 minutes, we covered much ground. We explored the layers of platform architecture, talked about the goals of platform engineering, and discussed how best to leverage open-source tools like Backstage, Kratix, and Terraform to create robust, scalable internal developer platforms.

The Multilayered Platform Approach

My introduction outlined the three layers of platform interaction: the application layer, platform orchestration, and the infrastructure layer. Each layer plays a crucial role in the overall functionality and efficiency of platform operations, with Terraform, Backstage, and Kratix serving as key components in infrastructure management, platform orchestration, and application choreography, respectively. 

Seve and Abby argued that a core platform-building goal is to abstract complexity away, allowing developers to focus on their core tasks without needing to manage the underlying infrastructure details directly:

"[From a UX perspective, you must ask] what makes sense to provide to the end developers? Having seen Kratix and the capabilities it provides as a middle layer, creating Promises and being able to abstract things away, I think it makes it easier to have these composable building blocks that you then push up into the portal UI layer."

Integration and Interoperability

One of the highlights included discussing how Terraform and Backstage integrate to provide a cohesive environment. Terraform, known for its strength in infrastructure as code, complements Backstage’s ability to streamline the application deployment processes.

Combining the two tools enables teams to manage infrastructure and deployment pipelines more effectively, ensuring that platform engineers can provide better support to application developers. However . . .

Challenges and Considerations

. . . Integrating these technologies is not without its challenges. Backstage's flexibility, for instance, while a considerable advantage, can also lead to complexity if not correctly managed. The key is to strike the right balance between customization and simplicity, ensuring that the platform remains accessible to all users without overwhelming them with options. 

All of the participants shared insights into how organizations could navigate these challenges:

"It's about choosing the right level of abstraction and making sure that the tools are not just powerful but also approachable. This often means hiding the complexity behind intuitive interfaces and focusing on the user experience."

However, everyone cautioned about the need to identify requirements for upgrading applications, services, and infrastructure. A platform (and portal) has to be built for days one, two, and two thousand to provide a positive experience for the users and a positive return on the investment for the business.

Future Directions and Best Practices

Looking ahead, we touched on the future of internal developer platforms, underscoring the importance of viewing platforms as products that require careful, thoughtful development. The discussion also moved toward best practices for platform engineering, emphasizing the strategic integration of new technologies.

Abby highlighted the need for platforms to evolve continuously to meet changing developer needs and adapt to new technological advancements. "As technology commoditizes certain aspects of platform engineering, platform teams must focus on adding value through unique services tailored to their specific business context," she explained.

Key Takeaways and Closing Thoughts

The fireside chat concluded with a case study discussion, during which Seve and Abby shared their experiences and advice on specific platform engineering challenges. The key takeaways were clear: successful platform engineering requires a deep understanding of both the tools available and the needs of your end-users, most typically the stream-aligned development teams.

As we wrapped up the discussion, it was evident that the combination of Terraform and Backstage is more than just a technical integration: it's a strategic approach to building more efficient, user-friendly platforms that empower developers to achieve their best work.

You can download the slides via Speaker Deck and watch the full discussion below. Many thanks to Seve for taking the time to join us and for sharing all of his great insights and experiences!

Video

Open source Tool Day One (app) Terraform (software) platform engineering

Published at DZone with permission of Daniel Bryant. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Death by a Thousand YAMLs: Surviving Kubernetes Tool Sprawl
  • The Open Source Climate Stack: Essential GitHub Repos Powering the Decarbonization Movement
  • Automatic Code Transformation With OpenRewrite
  • Internal Developer Portals: Modern DevOps's Missing Piece

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook