Microservices

What is the microservices architecture and how it compares to other popular architectural styles?

Transcript

1. Microservices Julián Espinel 2015-02-14
2. Agenda 1. A few software architectural styles (fast!) 2. Microservices architecture a. What is it? b. How old is this style? c. Why to use microservices? 3. Comparison between styles a. Monolithic b. SOA c. Microservices
3. Agenda 4. Benefits and challenges a. Technical b. Management 5. Should I use microservices? a. Yes, if you love challenges! b. Yes, if you want to learn and have fun! 6. Advice to implement microservices a. Technical b. Management
4. Agenda 7. Q&A 8. References 9. Thanks!
5. 1. A few software architectural styles (fast!) An example: NYPL Software Architecture?
6. 1. A few software architectural styles (fast!) Citizens Books Staff
7. 1. A few software architectural styles (fast!) What are we going to evaluate? 1. Development 2. Tracing (debugging) 3. Testing 4. Deployment 5. Scalability 6. Maintainability
8. 1. A few software architectural styles (fast!) Monolithic
9. 1. A few software architectural styles (fast!) Monolithic
10. 1. A few software architectural styles (fast!) Monolithic 1. Development 2. Tracing (debugging) 3. Testing 4. Deployment 5. Scalability 6. Maintainability
11. 1. A few software architectural styles (fast!) SOA Great theory, poor implementation.
12. 1. A few software architectural styles (fast!) SOA SOA
13. 1. A few software architectural styles (fast!) SOA ESB Staff entry Readers entry
14. 1. A few software architectural styles (fast!) SOA ESB V1
15. 1. A few software architectural styles (fast!) SOA ESB V2
16. 1. A few software architectural styles (fast!) SOA
17. 1. A few software architectural styles (fast!) SOA 1. Development 2. Tracing (debugging) 3. Testing 4. Deployment 5. Scalability 6. Maintainability
18. 1. A few software architectural styles (fast!) Microservices V1
19. 1. A few software architectural styles (fast!) Microservices V2 Proxy
20. 1. A few software architectural styles (fast!) Microservices V3
22. 1. A few software architectural styles (fast!) Microservices 1. Development 2. Tracing (debugging) 3. Testing 4. Deployment 5. Scalability 6. Maintainability
23. 2. Microservices architecture "Designing software applications as suites of independently deployable services." Martin Fowler
24. 2. Microservices architecture Each service: 1. Responsible for a business capability. 2. Run in its own process. 3. Independently deployable.
25. 2. Microservices architecture
26. 2. Microservices architecture What does a piece of software need in order to be independently deployable?
27. 2. Microservices architecture
28. 2. Microservices architecture
29. 2. Microservices architecture Each service: 1. Responsible for a business capability. 2. Run in its own process. 3. Independently deployable.
30. 2. Microservices architecture Do services communicate among them? How?
31. How to communicate microservices?
32. How?
33. How?
34. How? A staff member adds a new book
35. How? A staff member adds a new book
36. How?
37. How? If you do this, please do not put business logic into the ESB.
38. How?
39. How?
40. How? SOAP? REST?
41. How? SOAP? Modify the endpoints a bit and your clients will be this happy!
42. How? REST? Evolve your APIs with ease, make your devs and customers happy.
43. 2. Microservices architecture How to communicate your services? As always in software architecture it depends on your needs. But...
44. 2. Microservices architecture Ask yourself these questions: 1. Am I designing to scale? 2. Are my microservices fault tolerant? 3. Does my architecture have SPOFs? 4. Will the architecture be maintainable over the time? 5. Could I evolve the system without breaking clients?
45. 2. Microservices architecture How old is this style?
46. 2. Microservices architecture How old is this style?
47. 3. Comparison between styles 1. Monolithic 2. SOA 3. Microservices
48. Monolithic 3. Comparison between styles
49. Monolithic 1. Development 2. Tracing (debugging) 3. Testing 4. Deployment 5. Scalability 6. Maintainability 3. Comparison between styles
50. SOA ESB Staff entry Readers entry 3. Comparison between styles
51. SOA 1. Development 2. Tracing (debugging) 3. Testing 4. Deployment 5. Scalability 6. Maintainability 3. Comparison between styles
52. Microservices V1 3. Comparison between styles
53. Microservices 1. Development 2. Tracing (debugging) 3. Testing 4. Deployment 5. Scalability 6. Maintainability 3. Comparison between styles
54. Development Tracing Testing Deployment Scalability Maintainability Monolithic SOA MS 3. Comparison between styles
55. 4. Benefits and challenges Benefits -> Technical 1. Design for scale. 2. Improve system availability. 3. Pick the best languages and tools according to the task. 4. Build a service once, then reuse it.
56. 4. Benefits and challenges Benefits -> Technical
57. 4. Benefits and challenges Benefits -> Technical 5. Small services, less code per service, improve maintainability per service.
58. 4. Benefits and challenges Benefits -> Management 1. Develop services independently. 2. Create interdisciplinary teams. 3. Work in small teams.
59. 4. Benefits and challenges Benefits -> Management
60. 4. Benefits and challenges Challenges -> Technical 1. How to test integration between services? 2. How to test integration between services and clients? 3. How to deploy? Centralized or Distributed? 4. CAP theorem.
61. 4. Benefits and challenges Challenges -> Technical
62. 4. Benefits and challenges Challenges -> Technical 5. Service discoverability? 6. How to maintain systems written in different programming languages? Do you have devs for that?
63. 4. Benefits and challenges Challenges -> Management 1. Service governance? 2. Real full stack developers (DevOps)
64. 5. Should I use microservices? Again: as always in software architecture it depends on your needs and everything is a tradeoff.
65. 6. Advice to implement microservices Design your system (set of microservices) by business responsibility.
66. 6. Advice to implement microservices Make sure you have a reasonable unit tests coverage and CI. "Only then you will go home and rest in peace."
67. 6. Advice to implement microservices Define a deployment policy. 1. Centralized 2. Distributed 3. Mixed
68. 6. Advice to implement microservices Measure, measure, measure! Are your systems up? Do we need to scale now? May be in 15 minutes?
69. 6. Advice to implement microservices Dropwizard + Metrics HTTP REST HTTP REST Front-end Back-end
70. 7. Q&A
71. 8. References 1. http://martinfowler.com/articles/microservices.html 2. http://www.thoughtworks.com/insights/blog/microservices-nutshell 3. http://sanderhoogendoorn.com/blog/index.php/microservices-the-good-the- bad-and-the-ugly/ 4. http://microservices.io/patterns/monolithic.html 5. https://msdn.microsoft.com/en-us/library/ee658117.aspx 6. https://msdn.microsoft.com/en-us/library/aa480021.aspx 7. http://www.javaworld.com/article/2071889/soa/what-is-service-oriented-arc hitecture.html
72. 9. Thanks!