Best of Platform Engineering — October 2025

  1. 1
    Article
    Avatar of salesforceengSalesforce Engineering·28w

    Architecting Multi-System Production Platform

    Salesforce built Digital Wallet, a consumption-based pricing platform serving 15,000+ organizations and generating $400M+ in annual contract value. The engineering team overcame significant challenges as Data Cloud's first customer, including implementing SOX-compliant metadata security through Strict System Mode, building a custom event subscriber processing 20M daily events, and architecting failover strategies for near real-time usage tracking. The platform integrates multiple systems using fan-out mechanisms for entitlement sync, implements Spark job failover between EMR-on-EKS and EMR-on-EC2 to avoid rate limits, and maintains billing accuracy through architectural separation of hourly customer-facing updates from monthly financial reconciliation. The system includes high-cardinality monitoring, automatic retry logic, and a month-long buffer for usage reconciliation before billing.

  2. 2
    Article
    Avatar of earthlyEarthly·32w

    Backstage Adoption Guide: When to Use Spotify's Developer-Portal Framework

    Based on interviews with 20+ engineering teams, this guide examines when Backstage (Spotify's open-source developer portal framework) makes sense for organizations. Backstage works best for teams with 30+ engineers, multiple microservices, and 3-5 dedicated maintainers who can handle React/TypeScript. The framework isn't free despite being open-source—expect $380-650k annually for DIY implementation versus $84k for managed alternatives. Common pitfalls include underestimating frontend skill requirements, forcing 100% adoption, and lacking executive sponsorship. Success requires focusing on specific pain points (onboarding, service scaffolding, documentation), measuring ROI through metrics like time-to-first-PR and MTTR, and treating the portal as an internal product with iterative rollouts.

  3. 3
    Article
    Avatar of medium_jsMedium·28w

    Building a Kubernetes Platform — Think Big, Think in Planes

    Introduces a mental model for building Internal Developer Platforms by thinking in horizontal 'planes' rather than vertical layers. Explains five key planes (Developer, Integration/Delivery, Monitoring/Logging, Security, and Resource) and provides deep dives into Control, Observability, and Service planes. Uses OpenChoreo as a case study to demonstrate how this architecture enables scalable, secure-by-default platforms that centralize control while distributing scale across multiple Kubernetes clusters.

  4. 4
    Article
    Avatar of giantswarmGiant Swarm·29w

    The Gateway API shift: how Kubernetes networking actually works at scale

    Gateway API is replacing Kubernetes Ingress as the standard for traffic management at scale. Unlike Ingress, which relies on controller-specific annotations and lacks proper role separation, Gateway API provides a structured model with GatewayClass, Gateway, and Route resources that enable platform teams to manage infrastructure while application teams control routing rules. It supports advanced features like GRPC routing, service mesh integration through GAMMA, and safe cross-namespace delegation via ReferenceGrant. The API includes conformance testing for portability across controllers and vendors, making it suitable for multi-cluster, multi-team enterprise environments where consistent, scalable networking is critical.

  5. 5
    Article
    Avatar of tcTechCrunch·30w

    Automattic CEO calls Tumblr his ‘biggest failure’ so far

    Automattic CEO Matt Mullenweg acknowledged Tumblr as his biggest failure, citing the platform's unprofitability despite hosting over 500 million blogs. Plans to migrate Tumblr to WordPress infrastructure remain on hold due to high costs and the platform's inability to generate sufficient revenue. The company has attempted cost-cutting through layoffs and resource reallocation, but Tumblr continues to be sustained by profits from other Automattic products. Mullenweg also discussed ongoing projects including WordPress Playground, Beeper messaging app expansion, and the ongoing legal dispute with WP Engine over open source contributions.

See all Platform Engineering archives