We are adopting Port as a company IDP in the newly formed Platform Engineering team and we are liking it so far. We have reviewed a couple of other IDPs before settling on Port. The UI is pretty neat. Terraform provider could be improved. And the team behind Port is very enthusiastic
@@DevOpsToolkit Being a platform developer myself I am a bit hypocrticial when it comes to my own opinions about third party platforms, especially ones that you build important infrastructure on. If its not open source and its a SaaS solution who tells me it will still be around next year, in two years, in 5 years? There have been other SaaS offerings that basically died out because they were either bought or just didn't bring in enough revenue, in that case I'm out of luck and stranded without a dev portal.
For sure Port has much nicer UI. For me backstage UI is a little bit outdated. Backstage can be also extended with a custom components. Power of backstage is in the plugins. Based on this year eu kubecon I can say there is a huge hype on backstage. There is a need across organization to organize this microservice chaos. Finally there will be a change in this plugin core and it will be less messy in the future. That should empower backstage even more.
This is a very well made video. Especially the first seven minutes where you are walking and manage to get all shots without any other humans in the background, and manage to keep eye contact without running into things (at least in the edited final version). I have to imagine that it took at least a few takes. Excellent production quality. And the content is easy to follow, as always. The community appreciates the effort that you put into these videos. Thanks.
I’m using Port for a while, after I had a long trial on Backstage (and another managed solution) and I must say it made such a huge impact on our internal processes and gave great observation about what is going on in our infra. Another great thing to say is it didn’t take much time to make the integration. The platform is flexible and Port team are super helpful.
omg. This is really awesome. Thank you again. Please release more data models or awesome blueprints because like you said it want more predefined type of template, a litte bit tough when start. And one more, don't have self-host, sensitive credential, info put on that, is safe? Thank you!
Great video and spot on with you pro/con summary. I think a couple of those features have been (at least partially) implemented already which is a good sign as demonstrates they're open to feedback and rapid development. I think the examples could better and in Go instead of Python. I agree YAML should be an option too. Homepages/dashboard - spot on. Some nice visualisations and automatic reporting would be great and also enhanced search. I only added a small number of Blueprints for things like K8s clusters, ArgoCD and GitLab repos and already I was struggling to find things quickly. Overall though - a much better DevUX experience than Backstage and much more maintainable long-term. Some improvements to make, but certainly off to a fantastic start.
It would be great to if you could do a video on "proper storage" with Kubernetes not volumes and stuff but actual underlying storage, also networking with a cluster at scale how to ensure namespace separation for apps while providing advanced features such as dpdk and sriov, running this in a larger environment over 20 nodes, challenges and so on.
Nice video. The problem that I see here is the security implications giving third parties a ring to rule them all. Its possible to install it in bare metal with a license? Regards.
I don't think there is the option to self-host it :( That being said, I don't think it's a big deal (as long as you can actually use SaaS) since it's ingesting data that is not (typically) confidential.
@@DevOpsToolkit Interesting? Would love to see if other seem to have similar problems. Tried Different browsers (Brave, Chromium, edge) and even different computers and same issue. Comes up with an error "Please login with your work email to start using port"
I wanted to give OpsLevel a go but there is no (obvious) way to try it out without going through the sales motion. I tend to avoid services that do not have a free option or a clear pricing table. I think it's fair to pay for services, but I also think that there should be no obstacles to try that service first.
Port seems to do the kube/infra mgmt second to none on the market atm. However the scorecards in OpsLevel are a better experience. You can also run campaigns on improvements. OpsLevel will be launching Infrastructure cataloging soon but that feature seems mostly about seeing dependencies as they relate to services. I suggest you give them both a try if you are in the market for a SaaS IDP.
Arg, another tool circling around PRs and Services. 😮💨 I want proper trunk based development, feature flag, post commit code review and CI/CD service-deployment tooling for my teams 😮💨 😮💨 😮💨
Port is all about having a customizable UI that represents resources and enables actions related to them. You are still free to do trunk based development or whatever else you might be doing.
@@dinoscheidt Lazy devs (those who procrastinate) are the best ones. They tend to figure out how not to do something (typically through automation) rather than to continue doing the same thing over and over again. So, big thumbs up for procrastination.
