Reactive Microservices with Vert.x
2 likes1,580 views
The document discusses the evolution and importance of microservices, highlighting the shift from monolithic to responsive, resilient, and elastic architectures in software development. It emphasizes the necessity of being responsive to user needs, potential failures, and scalability issues, particularly in today's mobile and cloud-based environments. It also introduces Vert.x as a lightweight, reactive middleware solution that facilitates non-blocking, event-driven programming to enhance performance and scalability.
Reactive Microservices with Vert.x
- 1. Microservices In the beginning there was Vert.x
- 2. Braz, Anderson Software Engineer Java Man since 2000, postgradute, open source contributor, speaker and training consultant mrbrazjava
- 6. Why is responsiveness now more important than ever? Mobile Devices Cloud Environment Multicore Architecture Real-timeInteractive Collaborative
- 7. Reactive “Readly responsive to a stimulus” Responsive (React to Users) Resilient (React to Failure) Elastic (React to Load) Message Driven (React to Events)
- 8. Message Driven “The flow of the program is determined by events”
- 9. Immutability Avoid share mutable states and objects
- 10. Avoid Blocking Kills Scalability and Performance
- 11. Elastic “Capable of being easily expanded or upgraded on demand”
- 12. How do I know if I have a performance problem?
- 13. How do I know if I have a scalability problem?
- 14. The network is inherently unreliable
- 15. Embrace the network “Be of the web, not behind the web”
- 16. Location Transparency “It is not about ESB stupid”
- 17. Resilience “The capacity to recover quickly from difficulties”
- 18. Old school way
- 19. Old school way Error Response Worst in a Multi Thread
- 20. Worst in a Multi Thread Old school way
- 22. Doing Better Failure is an Event Avoid Cascading Manage locally Isolate the failure
- 23. Responsive “Quick to respond or react appropriately”
- 24. Asynchronous Events Loosely coupled architecture Lower Latency Better Throughput
- 28. Event Bus Point 2 Point Pub/Sub Handlers Addressing
- 29. Server and Client HTTP/S and TCP
- 30. File System Both Blocking and Non-blocking
- 31. Shared Data Local and Distributed using Hazelcast
- 32. High Availability Cluster Manager using Hazelcast with automatic failover
- 33. Rich Ecosystem Asynchronous JDBC, Mongo, Redis Web & Microservices Autentication & Ãuthorization Metrics (Dropwizard) Openshift & Docker Unit Test
- 34. Braz, Anderson Software Engineer Java Man since 2000, postgradute, open source contributor, speaker and training consultant mrbrazjava