Tag: platforms
-

DIY Platform – don’t do it
Here’s the 15 minute version of my overview of why you should buy your platform instead of building it. It’s based on the paper I co-authored on the topic. You can find the slides here, and there’s also a longer version of the talk from cfgmgmtcamp 2026. If you want to see more of my…
-

Platform as a Product, 2017 to 2026 – not much changed, which is the point
The Platform as a Product paper, first published in 2017 and updated for 2026. The concept survived Pivotal, the platform engineering category, and kubernetes blocking out the sun for five years.
-
Defeating Conway’s Law
Try using a platform to combat Conway’s Law and organizational friction caused by too many groups/silos. This matters because it removes the structural excuse for fragmentation. When a single platform surfaces all the controls a unified team needs, there is no longer a technical reason to keep five separate teams in five separate rooms. The…
-
Internal Developer Platform: Insights from Conversations with Over 100 Experts – Looks comprehensive!
-
Delivering Great Developer Experiences with Platform Engineering – A whole lot of first hand accounts of building and running developer platforms. (1) the platform should include CI/CD tooling, and I presume how to package and configure apps for production, (2) use developer surveys to track usage and needs, (3) product manage the platform, with a…
-
Patterns vs Platforms – It’s all hard stuff. Instead of centralized platforms, perhaps consider public cloud instead, mixed with conventions. Variation: don’t build your own platform, outsource it to a vendor/cloud.
-
The Care and Feeding of Internal Developer Platforms – Five benefits of monitoring and managing internal developer platforms are noted: improved system performance, cost reduction, scalability, enhanced security, and improved feedback loops. Achieving these benefits entails securing deployment environments, establishing system baselines, setting up alerting rules, monitoring application performance, and automating processes.
-
Link: Comparing Kubernetes to Pivotal Cloud Foundry — A Developer’s Perspective
Exactly what it says. The install and ops experiences are not covered, of course. Original source: Comparing Kubernetes to Pivotal Cloud Foundry — A Developer’s Perspective
-
The platforms were ultimately product-driven, not client-driven, and built in silos without collaboration. Currently, advisers are forced to go to five different places to do their work, often times duplicating functions in ways that are incredibly inefficient and not intuitive. Merrill expects this new consolidated platform will simplify the adviser and client experience in a…




You must be logged in to post a comment.