In our most recent webinar, we delved into the intriguing convergence of Terraform and Backstage, two pivotal technologies reshaping the landscape of platform engineering. This session was particularly exciting for us at Syntasso as we had a special guest, Seve Kim, a product manager from Backstage, joining Abby and Daniel!
Although the webinar only lasted 30 minutes, we covered a lot of ground. We explored the layers of platform architecture, talked about the goals of platform engineering, and discussed how best to leverage Backstage, Kratix, and Terraform to create robust, scalable internal developer platforms.
You can download the slides via the Syntasso Speaker Deck and watch the webinar recording via LinkedIn or the YouTube embedding below. We've also embedded several 30-second highlight clips in the article.
The multilayered platform approach
Our discussion kicked off with an introduction by Daniel, outlining 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.
The essence of good platform abstractions
A significant portion of our webinar focused on the importance of creating good abstractions within a platform. Seve emphasized the necessity of designing platforms that cater directly to the needs of end-users—typically developers—who require tools that simplify rather than complicate their workflows.
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 have to 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 of the discussion was 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.
The combination of 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. The flexibility of Backstage, 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, the webinar 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 towards best practices for platform engineering, with an emphasis on 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, it's crucial for platform teams to focus on adding value through unique services tailored to their specific business context," she explained.
Key takeaways and closing thoughts
The webinar concluded with a case study discussion, where participants 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 at your disposal and the needs of your end-users.
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.
Abby and I are somewhat biased, but we argued that to make this integration work not only for day one but also for day two and day 2000, implementing a platform orchestration layer using a tool like Kratix can provide more effective abstractions for teams to collaborate across.
For those who missed the live event, you can find the full recording on our YouTube channel (embedded below).
Many thanks to Seve for taking the time to join us and for sharing all of his great insights and experience!
Learn more
You can learn more about building platforms from these resources:
Any questions? Please get in contact!
We are always keen to answer more questions, so please contact us or join the Kratix OSS Slack.
Stay tuned for more updates, and keep pushing the boundaries of what your platforms can achieve on day two and day two thousand!
Comments