This presentation is about my talk on TDC 2017. It is an invite for you to understand and know more about reactive programming and vert.x to develop your microservices.

1. Reactive Microservices with
Vert.x

2. Principles & Practice

3. Why are microservices so
popular?

4. But...
distributed system are hard

5. That’s where reactive comes in

6. Reactive software reacts and
adapts its behavior based on the
stimuli it receives

7. Reactive System
An architecture style
used to build
responsive and robust
distributed systems
based on asynchronous
message-passing
Reactive Programming
A development model
focusing on the
observation of data
streams, reacting on
changes, and propagating
them.

9. Reactive Streams
Reactive streams is an initiative to provide a
standard for asynchronous stream processing with
back-pressure

10. Back Pressure
when n > m, please wait!
n n
mm
Producer Consumer

11. Reactive Systems
Elasticity
The ability to scale horizontally (scale out/in)
Resilience
The ability to handle failure and recover
Responsive
The most important thing for all companies
Asynchronous message-passing

12. Reactive Microservices
Autonomy & Isolation
adapt to the availability or unavailability of the services
surrounding them
Resilience
The ability to handle failure and recover
Asynchronisity
The most important thing for all companies
Elasticity
The ability to scale horizontally (scale out/in)

13. What about Vert.x?

15. Don’t block the event loop.

16. Multi-reactor principle

17. Verticles
Scalable
Non-Blocking
Simple

18. Worker Verticles
Worker Loop
Non-Concurrent
Blocking

19. Event Bus
Publisher and Subscribe
Point 2 Point
Clustered

20. Shared Data
Local and Distributed using
Hazelcast

21. High Availability
Cluster Manager using Hazelcast
with automatic failover

22. Talk is cheap, show me the
code...

23. mrbrazjava
I help developers and architects to be more productive on
distributed system development for them to be recognized as
references in the market. geracaosucesso.com