Microservices Day London 2017
who it's for
software architects, platform engineers, engineering managers, devops engineers, site reliability engineers, technical leads, product managers
topics
UpRing pub/sub systems; event-driven architectures; microservice architecture design; service mesh and network fabric; microservices security practices; highly scalable microservice patterns; organisational change for microservices; autonomous cross-functional teams; digital delivery for retail and fast food; evolutionary architecture and migration; microservice performance tuning
| title | author | length |
|---|---|---|
| The Highlights | 02m | |
Venue: 8 Northumberland Avenue, London
Event: Microservices Day London
Website: www.microservicesday.com | ||
| Building a Scalable Pub/Sub system with UpRing | Matteo Collina | 21m |
A working demo of UpRing shows a Node-based P2P system that shards keys on a consistent hashring and routes live connections (SSE/WebSocket) to the node owning… | ||
| Designing Microservice Architectures | Richard Rodger | 29m |
Argues that you design around messages not services and shows concrete patterns — synchronous vs asynchronous, pub/sub, scatter‑gather — with hexagon diagrams… | ||
| Delivering Digital to a Fast Food Company | David Bochenski | 21m |
Builds an MVP on AWS using a Strangler pattern and moves from monthly releases to over 50 releases a day, with zero‑downtime CI/CD via Docker, ECS and… | ||
| 3 Years Of Getting It Mostly Right | Clifton Cunningham | 26m |
Three years of micro‑service work at Tes.com yields concrete outcomes: roughly 137 services, small engineering teams of 3–4 people who deploy with Docker and… | ||
| There and Back Again | Mark Little | 27m |
Argues measurable lessons from Red Hat and JBoss experience: microservices often just reintroduce classic distributed‑systems failures and tradeoffs… | ||
| Building a Secure, Performant Network Fabric for Microservice Applications | Owen Garrett | 31m |
Compares three concrete network architectures — proxy model, router mesh, and a fabric model that embeds NGINX Plus as a sidecar — showing how service… | ||
| Pros/Cons of Highly Scalable Microservice Systems | Clifton Cunningham, Owen Garrett, Matteo Collina, Mark Little | 33m |
Panelists argue most projects never need global scale and advise first asking whether 200,000 concurrent users is actually required; companies report a working… | ||
| Autonomous Teams in Technology Organisations | David O'Donoghue | 34m |
Zalando adopts a radical agility model: roughly 180 autonomous teams (4–8 people each) given choice over tech, architecture and planning, supported by three… | ||
| Pros/Cons of Microservices | Cassandra Shum | 26m |
Argues that micro services win when a specific bottleneck is extracted and scaled, with an example of pulling out payments (not rewriting the whole monolith)… | ||
| Organisational change centered around technology | David O'Donoghue, Clifton Cunningham, David Bochenski | 40m |
A three‑year transformation moves a monolith to microservices on public cloud using the Strangler pattern and a lighthouse team isolated to prove the approach… | ||
| The Highlights | 02m | |
A rapid montage of the event with clips of sessions and audience reaction that never shows technical detail or claims no code excerpts and presents no… | ||
| Microservices Day London | Cassandra Shum, ThoughtWorks | Cassandra Shum | 01m |
Claim: microservices let large enterprise systems scale and deploy features significantly faster. Evidence: describes using ThoughtWorks consultancy to roll… | ||
| Microservices Day London | David O'Donoghue, Zalando | David O'Donoghue | 01m |
Before micro-services teams have tight technical dependencies forcing simultaneous build test and release cycles and slowing delivery; after moving to… | ||
| Microservices Day London | Mark Little, RedHat | Mark Little | 01m |
Claims that scale your organization and break down your monolith into more easy consumable and deployable units and bring your release cadence down appear as… | ||
| nothing matches | ||