This message was deleted.

Unemployment office.

Too soon, too soon

"IDP", often spelling out what the acronym means. I've only demo'd it. It's still in development and not quite ready to roll out for consumption. I'm guessing within our team we'll probably call it "the portal".

Own names! Examples from the Platforms I’ve managed last few years: • Avalaunch • Starboost • Nebula • Comeet

Own name indeed. Our platform at ZF Digital is called "Infinity" (it comes with a logo, a tag line and even a sticker that you can stick to your laptop). From my experience, building a brand really helps in spreading awareness about the platform and communicating with your stakeholders.

@Juliano Marcos Martins article on the PE blog from last week. Their platform is called FURY. Always thought that was a very cool name😄 https://platformengineering.org/blog/unveiling-the-secrets-of-a-successful-journey-mercado-libres-internal-developer-platform

Nice, we also had a logo & stickers with Starboost :)

Thanks for all the ideas & references. ❤️

Please don’t just send a link without any context @Roni Floman

@Luca Galante apologies, you're 100% right! this is an article about Monday.com internal portal (no relation to port, they built it themselves). It's named spehra and they distribute swag to contributors (see shirt in banner).

cc @Corey Innis

IDP

makes me think of an identity platform. Or intrusion detection platform. I usually go for 'platform' then 'infrastructure'. Failing those I use the codename for the current generation.

what are the most common usecases people using an idp for nowadays?

sounds like a good topic for a separate thread topaz thinking

Services heavily used From my platforms: —> business app exposition to the Word —> onboarding —> new app/new team onboarding —> new developer onboarding (permissions management) —> troubleshooting and runtime capability for apps Sometimes also some Interactions with external vendors

good shout! @Marta Wozniak sorry for the notification

@topaz t I don't mind, I meant that more people might add their comments if it was a separate topic 😄 I'd be interested to read it for sure!

true, ill make a separate thread then

"business app exposition" is more related to exposing an app to public internet on a particular domain. It's repetivve, it's related more to networking than app logic - so I believe Platform Engineers should have a service for that

not sure ive heard of idps providing observability integration; wouldnt a dev just ask for datadog access; for example.

Yes, but connecting any business app to any observability tool is a work which does not provide any business value directly… so it should be done not by a developer, but a Platform Engineer

hey @Krzysztof H. you said nothing about your blogs being the best in terms of lego use and great arguments. I looked at them and - wow!

Legos are the best! :)

no doubt about that!

I'm a little late to the party, but in platform engineering, i know that the IDP is the overall platform. But we also call other things platforms... i.e. our kubernetes and cloud foundry runtimes are referred to as platforms that we've built/enabled. We even call our databases "database platforms". Is there a clear definition of how to use the term platform when developing an IDP?

The best one in my opinion is in Team Topologies :) a recommended reading for a person who starte the journey with Platform Engineering