Keynote Session Sponsored by CircleCI - Microservices: Just Another Tool in the Toolbox
summary
CircleCI starts by extracting a small set of services to fix operational scaling, finding that two services solve the 80/20 of their biggest problems rather than an all‑in rewrite. Decisions follow a concrete fitness function: five architectural values — functionally decoupled, fault‑tolerant, operator‑friendly, maintainable, economic — used to score changes. Examples: permissions get decomposed into a service when misaligned, Honeycomb is deployed for cloud observability while on‑prem integration is deferred, and transitions are prioritized over end‑state purity.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:33CircleCI's journey to Microservices
- 2:35What problems do you need to solve?
- 3:47Find the architecture for you today
- 5:50Fitness Function
- 7:37CircleCI's architectural values
- 11:07Examples for reevaluating values
- 14:14Summary: When to switch to Microservices?
related talks
49mKeynote
14mKeynote: Open Source & Operational Excellence
37mKnee Deep in Microservices
44mMicroservices: 5 things I wish I'd known
45mMicroservices: A retrospective
27mMicroservices Are ‘Easy’, Dependencies Are Hard
25mMaking microservices a behaviour not a buzzword
01h 03mThe Magic of Small Things - 10 Years of Microservices