Richard Rodger
where else to find them
what they talk about
all 6 in the filters
where they keep going back
- Microservices Day London2 editions2016–2017
all 6 in the filters
on a stage with
- Nix Crabtreeonce
who talks about the same things
- Nikita Galkin9 talks
- Fred George25 talks
- Malte Ubl25 talks
- Sebastian Springer13 talks
- Jimmy Bogard50 talks
- Rob Harrop4 talks
| title | conference | date |
|---|---|---|
| Architecting for Change Debate | UXDX Europe 2019 | 2019-10-07 |
Debate lays out a concrete tradeoff: starting with 10 endpoints as separate microservices means 10 codebases, 10 pipelines and 10 data stores upfront; the… | ||
| Designing Microservice Architectures | Microservices Day London 2017 | 2017-05-25 |
Argues that you design around messages not services and shows concrete patterns — synchronous vs asynchronous, pub/sub, scatter‑gather — with hexagon diagrams… | ||
| Solving service discovery: Node.js microservices without a registry | Microservices Day London 2016 | 2016-05-10 |
Argues service discovery can be registry-free by using peer-to-peer membership and message patterning: implements the SWIM gossip protocol so each Node.js… | ||
| Node.js and Digital Transformation made for each other | NodeConfEU 2015 | 2015-09-06 |
Claims concrete results: PayPal measured twice as fast when using Node, the module system accounts for about half the platform’s advantage, and static-analysis… | ||
| Measuring Microservices | Microservices Day NY 2015 | 2015-07-13 |
Claims that system health is best judged by message flow rates and simple pattern-derived checks rather than per-service metrics, uses invariants as ratios… | ||
| Measuring Micro-services | Codemotion Rome 2015 | 2015-03-25 |
Argues that risk is reducible by measuring emergent behavior rather than CPU: track message flow rates and invariant ratios (e.g., add-item vs tax messages… | ||
| Microservices | NodeConf EU 2014 | 2014-09-08 |
Claims outcomes from ~50 projects show microservices reduce code size, enable independent deploys and let teams swap components without breaking others… | ||
| nothing matches | ||