Downloaded 153 times
Uploaded byRed Hat Developers
Vert.X: Microservices Were Never So Easy (Clement Escoffier)
Vert.x is a toolkit for building reactive and distributed applications on the JVM using asynchronous non-blocking code. It allows building microservices that are responsive, elastic, resilient and message-driven. Vert.x provides components for HTTP servers and clients, event bus messaging, distributed data structures, load balancing and failure handling to help build reactive microservices. The event bus is key to communication in Vert.x applications, allowing different parts of the system to asynchronously send and receive messages regardless of language or location. Reliability patterns like circuit breakers help applications gracefully handle failures that are inevitable in distributed systems.
More Related Content
Similar to Vert.X: Microservices Were Never So Easy (Clement Escoffier)
![Vert.x - Reactive & Distributed [Devoxx version]](https://cdn.slidesharecdn.com/ss_thumbnails/devoxxvertx-reactivedistributed-181211094022-thumbnail.jpg?width=640&height=640&fit=bounds)
Vert.X: Microservices Were Never So Easy (Clement Escoffier)
- 1. VERT.X M I CR O S E R V I C E S W E R E N E V E R S O E A S Y CLEMENT ESCOFFIER Vert.x Core Developer, Red Hat
- 2. VERT.X I N 1 0 S L I D E S . . .
- 3. V E RT. X I S A TO O L K I T T O B U I L D D I S T R I B U T E D A N D R E AC T I V E A P P L I C A T I O N S O N T O P O F T H E J V M U S I N G A N A S Y N C H R O N O U S N O N - B L O C K I N G D E V E L O P M E N T M O D E L .
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12. MICROSERVICES R E BR A N D I N G D I S T R I B U T E D A P P L I C A T I O N S
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21. HTTP & REST B E CA U S E I T A L W A Y S B E G I N W I T H A R E S T
- 22. VERT.X HELLO WORLD vertx.createHttpServer() .requestHandler(request -> { //Handler receiving requests request.response().end("World !"); }) .listen(8080, ar -> { // Handler receiving start sequence completion (AsyncResult) if (ar.succeeded()) { System.out.println("Server started on port " + ar.result().actualPort()); } else { ar.cause().printStackTrace(); } });
- 23.
- 24. E V EN T L O O PS
- 25. VERT.X ASYNC HTTP CLIENT HttpClient client =vertx.createHttpClient( new HttpClientOptions() .setDefaultHost(host) .setDefaultPort(port)); client.getNow("/", response -> { // Handler receiving the response // Get the content response.bodyHandler(buffer -> { // Handler to read the content }); });
- 26.
- 27. SERVICE DISCOVERY - KUBERNETES No need for publication - Import Kubernetes services HttpEndpoint.getClient(discovery, new JsonObject().put("name", "vertx-http-server"), result-> { if (result.failed()) { rc.response().end("D'oh no matching service"); return; } HttpClient client = result.result(); client.getNow("/", response -> { response.bodyHandler(buffer -> { rc.response().end("Hello " + buffer.toString()); }); }); });
- 28.
- 29.
- 30. MESSAGING WITH THE EVENT BUS T H E S P I N E O F V E R T . X A P P L I C A T I O N S
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39. RELIABILITY PATTERNS D O N' T B E F O O L , B E P R E P A R E D T O FA I L
- 40.
- 41. MANAGING FAILURES Distributed communication may fail vertx.eventbus().send(..., ..., new DeliveryOptions().setSendTimeout(1000), reply-> { if (reply.failed()) { System.out.println("D'oh, he did not reply to me !"); } else { System.out.println("Got a mail " + reply.result().body()); } });
- 42.
- 43. MANAGING FAILURE client.get("/", response ->{ response .exceptionHandler(t -> { // If the content cannot be read rc.response().end("Sorry... " + t.getMessage()); }) .bodyHandler(buffer -> { rc.response().end("Ola " + buffer.toString()); }); }) .setTimeout(3000) .exceptionHandler(t -> { // If the connection cannot be established rc.response().end("Sorry... " + t.getMessage()); }) .end();
- 44.
- 45.
- 46. CIRCUIT BREAKER cb.executeWithFallback(future -> { //Async operation client.get("/", response -> { response.bodyHandler(buffer -> { future.complete("Ola " + buffer.toString()); }); }) .exceptionHandler(future::fail) .end(); }, // Fallback t -> "Sorry... " + t.getMessage() + " (" + cb.state() + ")" ) // Handler called when the operation has completed .setHandler(content -> /* ... */);
- 47.
- 48. SCALABILITY PATTERNS B E P R E P A R E D T O B E F A M O U S
- 49.
- 50.
- 51.
- 52.
- 53.
- 55.
- 56.