Developer Experience Q&A
summary
Service Weaver claims 9x infrastructure cost reduction on a port of Online Boutique (11 microservices), attributing half the gain to runtime collocation and the other half to a custom encoder and transport; components expose internal listeners and use a sidecar for discovery and Kubernetes services, and current language support is Go with a plan for multi-language runtimes. Prospect runs intent-driven config and enforcement across production (including network switches) but struggles with slow intent generation and how to compose select-validate loops. Meta’s Thrift work adds async, streaming and safer IDL and requires dual-server migrations to replace gRPC.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:30Service
- 2:50Heterogeneity
- 4:18Biggest challenge
- 5:56Thrift Journey
- 7:12NonBackable Changes
- 8:40Component Communication
- 9:58Prospect
- 12:08Thrift
- 13:19Language heterogeneity
- 14:23Service Weaver deployment
- 15:01Closing remarks
related talks
32mSoftware development reimagined
14mUsing Reason in traditional Enterprises
15mDevX in the Internet Age: One Step Forward, Two Steps Back
26mTransforming Developer Experience The Good, the bad and the ugly
11mAddressing deployment speed and developer focus
37mPlatform Reality Has a Surprising Amount of Detail
26mClosing the Developer Experience Gap of K8s Development
21mImproving your Developer Experience Through Platforms and Generative AI