My new issue is out! After talking to hundreds of ...
# general
r
My new issue is out! After talking to hundreds of Platform Engineering teams in less than 6 months, I discovered how much most of them using (or who tried using) Backstage were struggling with it. What I heard is how much maintenance work it was required and how complex it was to build its own plugins and re-use what have already been done (Terraform / Shell…)… So is there another alternative to Backstage today? (some teasing here 😄 ). https://romaricphilogene.substack.com/p/platform-tips-20-why-backstage-is I’m also curious to get your experience. What looks like your experience with Backstage? Satisfied? Not satisfied? Why? thinking
t
I'm using the free tier of Port (getport.io). They have an active Slack community and respond well to customer feedback/issues there. I'm mostly using it as a pretty front end for self service actions.
They have a webpage comparing/contrasting Backstage https://www.getport.io/compare/backstage-vs-port
r
@Teddy What type of actions do you provide in self service?
t
It's really just a frontend to hit a web hook. Port http requests come from a known IP address pool, uses cryptography to sign the payload so you can validate it on the web hook, and provides Google login identity context so the web hook can ensure the user has permission to do the thing
Or I should say a frontend that sends http requests to a Cloud Functions service in GCP, which in turn invokes a Cloud Run job to do the thing
Actions include create/modify/destroy development instances of Cloud SQL, perform a deploy, refresh a lower environment
I'm holding off on setting up much inventory bc you are limited to 10,000 entities and I am not sure how I want to allocate and utilize them. If we change to the paid plan, you get unlimited inventory and you can just send everything to port all the time and provide that mystical "single pane of glass"
r
I spent several days just to make nice working Dockerfile
j
Atlassian's Compass is a great alternative to Backstage! I may be a bit biased, but I wish it had been around when I was a developer. 🙂