The reactive microservices can help us create more robust, more flexible and better positioned systems to meet the modern demands.

1. 1
Reactive
Microservices
@spinelli_edu

2. Software Craftsmanship
2
@spinelli_edu

3. We Are!!!
3
@spinelli_edu

4. 4
1. Deployment Independence: updates to an individual
microservice have no negative impact to any other
component of the system. Optimized for
Replacement.
2. Organized around business capabilities
3. Products not Projects
4. API-Focused
5. Smart endpoints and dumb pipes
6. Decentralized Governance
7. Decentralized Data Management
8. Infrastructure Automation (infrastructure as code)
9. Design for failure
10. Evolutionary Design
@spinelli_edu

5. Monolito vs. Microservices
5
@spinelli_edu

6. Reactive Manifesto
6
@spinelli_edu

7. Resilience
7
○ Registration and Discovery Service
○ Routing
○ Fault Tolerance
○ Security Management
○ Centralized Configuration
@spinelli_edu

8. 8
Spring Cloud with Netflix OSS
Centralized Configuration Spring Cloud Config +
Bus
Service Discovery Netflix Eureka
Load Balance Netflix Ribbon
Circuit Breaker Netflix Hystrix +
Turbine
Proxy Server Netflix Zuul
Security Spring Cloud Security

9. 9
Centralized Configuration

10. 10
Service Discovery

11. 11
Load Balance

12. 12
Circuit Breaker

13. 13
Proxy Server

14. 14
Security

15. ○ Distributed Deployment
○ Auto Scale
○ Orchestration
○ Redundancy
○ Monitoring
Elastic
15
@spinelli_edu

16. Deployment Distribuído
16
@spinelli_edu

17. Distributed Deployment
17
@spinelli_edu

18. Auto Scale
18
@spinelli_edu

19. Orchestration
19
@spinelli_edu

20. Redundancy
20
@spinelli_edu

21. Monitoring
Log Aggregatio
ELK, Sentry,
Logentries, Splunk.
Event Correlation
Spring Cloud Sleuth.
Tracing e Health
Check
Zipkin, HTrace,
Spring Boot Admin.
21

22. Tools
22
@spinelli_edu
AWS
ECS

23. Service Mesh
23
@spinelli_edu

24. Service Mesh
24
@spinelli_edu

25. ○ Asynchronous Communication
○ Non blocking I/O
○ Distributed Environment
○ Queuing
○ Consistency
○ Event sourcing
○ CQRS
Message-Driven
25
@spinelli_edu

26. Blocking I/O
26
@spinelli_edu

27. Non Blocking I/O
27
@spinelli_edu

28. “ Reactive
programming is
programming with
asynchronous data
streams.
28
@spinelli_edu

29. Opções
29
@spinelli_edu

30. CREDITS
▪ https://www.reactivemanifesto.org/
▪ http://blog.soat.fr/2018/01/les-systemes-reactifs-et-le-pattern-actor-model/
▪ https://bit.ly/2nnvJ01
▪ https://bit.ly/2A9ApQq
▪ https://developer.ibm.com/dwblog/2017/istio/
▪ https://istio.io/
▪
30
@spinelli_edu

31. 31
THANKS!
Any questions?
You can find me at:
▪ @spinelli_edu
▪ eduardosl.dev@gmail.com