12-factor Microservices

12-factor microservices, distributed systems and event driven architecture for ONS Software Engineer Community of Practice

Code is on GitHub: https://github.com/ONSdigital/software-engineer-cop-12-factor-microservices

Transcript

1. 12-factor microservices @ONSdigital ONSdigital Software Engineer Community of Practice
 29th November 2016
2. Hi, I’m Ian @iankent ian-kent
3. 12-factor microservices • What is 12-factor? • What are microservices? • What are distributed systems? • What is event driven architecture?
4. The twelve factors
5. The twelve factors • Portability between environments • Suitable for modern platforms • Supports continuous deployment • Can scale without significant changes Why use 12-factor?
6. The twelve factors • Codebase • Dependencies • Config • Backing services • Build, release, run • Processes • Port binding • Concurrency • Disposability • Dev/prod parity • Logs • Admin processes More info https://12factor.net
7. Any questions? The twelve factors
8. A baby names API
9. A baby names API What does it do? • One endpoint: GET /top10 • Simple JSON response:
10. A baby names API
11. A baby names API
12. Microservices
13. Microservices Microservice myths • Can be rewritten in two weeks • Less than 50 lines of code • More difficult to design • More difficult to build and deploy
14. Microservices What is a microservice? • Single responsibility • Bounded context • Well defined interfaces • Composable
15. Microservices Why use microservices? • Clear, concise code • Better fault tolerance • Lower risk deployments • Flexible technology choices
16. Microservices What are the challenges? • Interfaces • Distributed systems • Complex architecture • Build and deployment
17. Any questions? Microservices
18. Distributed systems
19. Distributed systems What are they? • Spread across physical servers, datacentre’s and continents • Coordinate by passing messages • Fail often, in unexpected ways • Suffers from CAP theorem
20. Distributed systems The fallacies • The network is reliable • Bandwidth is infinite • Topology doesn't change • Transport cost is zero • Latency is zero • The network is secure • There is one administrator • The network is homogeneous
21. Any questions? Distributed systems
22. A baby names API
23. A baby names API
24. A baby names API New requirement Registrars can provide data electronically
25. A baby names API What does it do? • One endpoint: POST /baby • Simple JSON input:
26. A baby names API
27. A baby names API So why not? • Complexity • Security • Scaling • Risk
28. A baby names API
29. Event driven architecture
30. Event driven architecture What is it? • Asynchronous • Fault tolerant • Scalable • Resilient under load
31. Any questions? Event driven architecture
32. A baby names API
33. A baby names API
34. A baby names API New requirement Provide a real-time stream of baby names
35. A baby names API What does it do? • One endpoint: GET /stream • Simple JSON output stream:
36. A baby names API
37. A baby names API So why not? • ~2k new babies per day • Atomic database updates • Top 10 changes infrequently • How does streaming work?
38. A baby names API Baby name events • New baby registration • Send to streaming API users • Update database • Has top 10 changed? • Notify output API
39. A baby names API
40. TL;DR
41. 12-factor microservices • What is 12-factor? • What are microservices? • What are distributed systems? • What is event driven architecture?
42. Thank you! @iankent ian-kent