Platform engineering is not just Backstage

[@asubmani]

Trying to follow along... the flow of this video is confusing... it repeatedly highlights the problem with backstage and then then the top item in the demo is err.. backstage? would love to see the problem and the solution as am lost if the demo is the recomended solution or if is highlighting problems with backstage!

[@tomask4453]

I had the same impression

[@asubmani]

Thanks for this demo.. checking out the demo section again... so if I have backstage and score, what value does having humanitec provide? I would like to understand it from POV of "This is what you would need to do without humanitec vs if you have humanitec... all these steps can be reduced"

[@asubmani]

Problems with Backstage and the netflix tool announced in Pcon22... ---->lots of "solution salad"---demo. I would need to look at the whole video again but would be nice if the speaker just says "this is what my demo architecture is: Backstage, code repo in TF etc..) not faulting the technical skills just the presentation of this with lot of back and forth.. I totally didn't get the part of the graph based approach before the demo? Is the demo using a graph based approach? or not?

[@LaurentPicquet]

(27:54) I like how easy it looks to upgrade postgres from v14 to v15 with just 1 line of code. That might be true for ephemeral resources, but your production db has had data created into it for weeks, months or years and won't be easy to upgrade without causing headache. Update one file? I don't think so...