More Related Content
What's hot
What's hot (17)
Similar to Reactive Microservices with eclipse vert.x
Similar to Reactive Microservices with eclipse vert.x (20)
Recently uploaded
Recently uploaded (20)
Reactive Microservices with eclipse vert.x
- 1. MONOLITHS TO MICROSERVICES: APP TRANSFORMATION Hands-on Technical Workshop Ram Maddali Senior Architect @RamMaddali rmaddali@redhat.com Anand Akella Senior Architect aakella@redhat.com
- 3. INSERT DESIGNATOR, IF NEEDED The 2 faces of Reactive Reactive A software showing responses to stimuli Reactive Systems Reactive Programming Akka, Vert.x Reactor, RX, Vert.x Actor, Agent Autonomic Systems Data flow, Functional programming
- 4. INSERT DESIGNATOR, IF NEEDED5 Eclipse Vert.x Vert.x is a toolkit to build distributed and reactive systems ● Asynchronous Non-Blocking development model ● Simplified concurrency (event loop) ● Reactive microservice, Web applications, IOT ● Ideal high-volume, low-latency applications ● Un-opinionated ● Understands clustering in its core architecture Home - http://www.vertx.io
- 5. INSERT DESIGNATOR, IF NEEDED6 VERT.X EVENT LOOP EVENT QUEUE EVENT LOOP WORKER THREADS async Handle Thousands of Requests With Few Threads response
- 6. INSERT DESIGNATOR, IF NEEDED8 ● Explore Vert.x Maven project ● Create an API gateway ● Run Vert.x locally ● Deploy Vert.x on OpenShift LAB 4: Reactive Microservices with Eclipse Vert.x
- 7. LAB: REACTIVE MICROSERVICES WITH ECLIPSE VERT.X
- 8. GOAL FOR LAB In this lab you will learn: ● How Event-based architectures supercharge microservice apps ● Use cases for reactive applications ● Develop microservices using Eclipse Vert.x ● Interact with other microservices without blocking ● Learn the basics of Reactive programming
- 9. CURRENT STATE OpenShift coolstore-prod Coolstore monolith Coolstore database (prod) inventory Inventory microservice Inventory database UI Future Services Future Services Future Services Future Services catalog Catalog microservice Catalog database
- 10. LAB: REACTIVE MICROSERVICES SCENARIO 6 BUILDING REACTIVE MICROSERVICES
- 12. RESULT OF LAB In this lab you learned how to: ● Build reactive web application that are non-blocking ● Asynchronously call out to external service using Callbacks, Handlers and Futures ● Deploy the application to OpenShift
- 14. ECLIPSE VERT.X OFFER MUCH MORE
- 15. INSERT DESIGNATOR, IF NEEDED17 SERVICE DISCOVERY Service Provider Service Provider Service Provider Service Consumer Service Consumer Service Consumer Vert.x Service Registry publish lookup Bridge Bridge Bridge import Kubernetes Consul Other
- 16. INSERT DESIGNATOR, IF NEEDED Vert.x vs NodeJS 2 threads per core NodeJS Vert.x Vert.x ● Multi-threaded ● Polyglot (Java, JavaScript, Scala, and more) ● Supports reactive programming using RxJava, RxJS, etc NodeJS ● Single threaded ● JavaScript only ● Support reactive programming using RxJS
- 17. INSERT DESIGNATOR, IF NEEDED19 FREE E-BOOKS http://vertx.io/docs/
Editor's Notes
- Single thread blocking was used
- Vert.x uses the Event Loop method to handle a large number of events (e.g. HTTP requests). Event Loop is a method for checking whether there is a new event in the queue, the event loop assigns a worker thread to handle the request and returns immediately to pick up the next event. This asynchronous architecture allows Vert.x to handle thousands of requests with just a single thread. Remember the golden rule of asynchronous architectures: Never block the event loop!
- Vert.x supports built-in service discovery by providing a mechanism for publishing and looking up services in the service registry. A service provider publishes existing services into the registry which allows the service consumers to look up a service based on their needs and discover those sevices. The service registry uses the Vert.x distributed data structure to store the service records and since it’s distributed, all members of the cluster have access to all the records. Vert.x can also use Redis and other backends to store the service registry data In addition to the service providers, Vert.x also supports bridges to be able to import service from other sources such as Kubernetes and Consul. The Kubernetes bridge enables Vert.x to import OpenShift/Kubernetes services into the service registry automatically and allow automatic injection of service coordinates into Verticles.