Revisiting Microservice Composition With The Delegator Pattern
summary
Claims an edge execution driver that moves orchestration to the edge and composes existing HTTP endpoints rather than replacing them. Implements a delegator pattern (an edge service plus registry and provisioner), a live prototype that uses a JQ-like Rust crate for payload transforms and an early cryptogram datagram for encrypted context. Authors report real migrations from a legacy GraphQL path into these smaller Python services, the system runs on laptop demos and saw production use during migration, and the approach actually reduces operational surface.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:49Microservices composition problem
- 3:57Monolith to tangled microservices
- 5:00Delegator Pattern concept
- 8:12Minimize network round trips
- 9:54Delegator Pattern in practice
- 12:46Virtual hosts and composition
- 15:41Live demo: data transformation
- 18:55Future of Delegator Pattern
- 21:22Architecture and ecosystem plans
- 24:33Q&A
related talks
27mProgressive Microservices with NodeJS
24mPatterns of Evolution from Monolith to Microservices
50mDistributed GraphQL APIs: Breaking Down Monoliths & Unlocking Agility for Dev Teams
31mChopping the monolith
41mLiving on the Edge (Service): Bunding Microservices
33mChopping the monolith
46mWhat Next After Microservices?
23mDerisking Migrations of API Backends