If you love data and data context formats for exchanging data, you will love this conversation.
Today’s episode is a deep conversation about the potential ability to define ways in which we produce, store and share data, providing context using markup languages, and then being able to extend that. It’s a fascinating conversation about how much we could improve our use of data if we were able to provide more context about who wanted to see it and what relevance it had.
We also have some interesting conversations about data migration and how we share information.
Today we talk about backstage.io, and we have that conversation centered around a demo done by one of the RackN and interns, Zander Franks. Check out the demo video here: youtu.be/cAQQOmKz4OI
Zander has been exploring with the backstage to Digital Rebar integration, and the conversation that results explains backstage in some fundamental ways and also what it takes to build good developer portals.
You will find in this episode both the broader information about how to do integrations where you have a developer portal as a front end and the key insights about how backstage works.
To get the most out of the backstage pieces, you will definitely want to see the video on Youtube. Take time to enjoy this whole podcast, both in video and audio format.
In the Cloud 2030 Podcast episode from January 10th, Rob Hirschfeld discusses the backstage integration, emphasizing the importance of understanding the dynamics involved in building an integration between a developer self-service portal and the systems responsible for a robust deployment experience. Hirschfeld underscores the critical point that while developer interfaces are crucial in platform engineering, they should not be expected to replace production tools like orchestrators, observability platforms, and infrastructure automation components. The episode features a demonstration and code exploration, providing valuable insights into the complexities and considerations of such integrations. For those interested in similar discussions, the Cloud 2030 community welcomes participation at the2030.cloud.
Good APIs are hard to design! Making them long lasting and scalable is even harder.
We discussed two aspects of API design. First, making about Event Bus for system integration and then RackN CTO, Greg Althaus, discusses what his team considers a good API design from Digital Rebar.
