Vert.x v3 - high performance polyglot application toolkit
•Download as PPTX, PDF•
14 likes•2,887 views
Presentation prepared by Bartek Zdanowski.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Vert.x v3 - high performance polyglot application toolkit
Similar to Vert.x v3 - high performance polyglot application toolkit (20)
More from Sages
More from Sages (20)
Recently uploaded
Recently uploaded (17)
Vert.x v3 - high performance polyglot application toolkit
- 1. vert.x v3 high performance polyglot application toolkit
- 3. Hello! developer @ vertx lover father and husband :) 3
- 4. vert.x 4
- 5. vert.x 5 Invented by Tim Fox as Node.x 24 June 2015 - released v3 still it’s very hot :D
- 6. vert.x buzzwords simple embeddable toolkit threadSafe concurrent asynchronous eventDriven reactive eventBus scalable polyglot 6
- 9. the problem number of mobile users raises 2,1 bln in 2012 -> 7 bln in 2018 Internet of things - 30 bln in 2020! IPv4 is exhausted IPv6 is already ready for all of them 9
- 10. the problem traditional synchronous approach ■one thread handles one task ■thread is waiting for job to finish ■whole queue of tasks waits 10
- 11. the problem traditional synchronous approach ■synchronous code ■scalability problem ■lots of threads ■concurrency that no-one understands ;) 11
- 12. the problem 12 Tomcat: 200 threads = 200 connections rest of incoming connections must wait*… *okay, now you can do nonblocking in Tomcat https://tomcat.apache.org/tomcat-7.0-doc/aio.html
- 15. the problem big thread pools are evil synchronous code is even more evil concurrency is very hard synchronous == blocking 15
- 16. the solution 16
- 18. the solution 18 1 task = series of loosely coupled events event that informs that new job/data is waiting
- 19. the solution 19 program should release thread instead of waiting for operation (I/O) to be finished use non-blocking IO (NIO)
- 21. the solution 21
- 24. vert.x 24 thread pool == double cores count actor like model
- 25. some code 25
- 26. 26 public class HelloVerticle extends AbstractVerticle { @Override public void start() { LoggerFactory.getLogger(getClass()).info( "Hello vert.x"); } }
- 27. 27 public static final String CONSUMER_ADDRESS = "consumer.address"; public void start() { vertx.eventBus().consumer(CONSUMER_ADDRESS, new Handler<Message<String>>() { public void handle(Message<String> message) { logger.info("Got message:" + message.body()); } }); } //Java < 8
- 28. 28 public static final String CONSUMER_ADDRESS = "consumer.address"; public void start() { vertx.eventBus().consumer(CONSUMER_ADDRESS, message -> { logger.info("Got message: " + message.body()); }); } //Java 8 Lambdas FTW!
- 30. threadsafe 30 class MyService { public synchronized Result doSomething(Data data) { //do some critical stuff } }
- 31. threadsafe only when one thread! 31 class MyService { public synchronized Result doSomething(Data data) { //do some critical stuff } }
- 32. threadsafe particular verticle runs in one thread! 32
- 33. 33 verticle
- 34. 34 basic deployment unit actor-like model (akka similarity) always run in the same thread can have many instances verticle
- 35. verticle threadsafe code ■verticle instance - always the same thread ■can have separated classloaders for each verticle instance 35
- 36. verticle threadsafe code ■event bus separates threads ■shared data: maps, counters, locks 36
- 38. let’s code! 38
- 39. ■hello world vert.x - first verticle ■deploying other verticles ●one instance ●many instances ●other after successful deployment ●deployment options ●passing config 39 let’s code! S1
- 40. ■running from IDE ■running from command line ●java -jar ●vertx run 40 let’s code! S1
- 41. 41 eventBus
- 42. 42 eventBus
- 43. 43 eventBus
- 46. 46 eventBus Publisher - subscriber publish() //broadcast like JMS Topics, no replying
- 47. 47 eventBus p2p send() //point-to-point like JMS Queues, can reply
- 48. 48 eventBus p2p send() //point-to-point like JMS Queues, can reply round robin
- 49. 49 eventBus p2p send() //point-to-point like JMS Queues, can reply round robin
- 50. 50 public void start() { getLogger().info("Broadcaster started"); vertx.setPeriodic(PERIOD_MS, timerID -> { getLogger().info("Broadcasting message " + counter); vertx.eventBus().publish(Consumer.CONSUMER_ADDRESS, "Message " + counter); counter++; }); } Broadcasting a message
- 51. 51 public void start() { getLogger().info("Broadcaster started"); vertx.setPeriodic(PERIOD_MS, timerID -> { getLogger().info("Broadcasting message " + counter); vertx.eventBus().send(Consumer.CONSUMER_ADDRESS, "Message " + counter); counter++; }); } Sending a message p2p
- 52. 52 public void start() { getLogger().info("Consumer started! " + hashCode()); vertx.eventBus().consumer(CONSUMER_ADDRESS, message -> { getLogger().info("Received message: " + message.body()); }); } Consuming a message
- 53. public void start() { getLogger().info("Consumer started! " + hashCode()); vertx.eventBus().consumer(CONSUMER_ADDRESS, message -> { getLogger().info("Received message: " + message.body()); message.reply("I got your message"); }); } 53 Consuming a message + replying
- 54. let’s code! 54
- 55. ■periodic events ■sending/receiving events ●publish-subscribe / broadcast ○ one producer ○a few consumers 55 let’s code! S2
- 56. ■sending/receiving events ●point2p ○one consumer ○one consumer with response ○ a few consumers with response 56 let’s code! S2
- 57. web client 57
- 58. 58 HttpClientOptions opts = new HttpClientOptions() .setDefaultHost("some.host.com"); HttpClient client = vertx.createHttpClient(opts); client.get("/request/uri").handler(resp -> { resp.bodyHandler(bodyBuffer -> { System.out.println("here's the body"); System.out.println(bodyBuffer.toString()); }); }).end(); http client
- 59. ■pulling data from http server ■parsing data with multiple verticles 59 let’s code! S3
- 61. 61 lightweight vert.x core extensions ■web ■data access (mongoDB, redis, JDBC) ■security (basic auth, jdbc auth, jwt, shiro) ■reactive (based on RxJava) ■others vert.x ecosystem
- 62. 62 web server
- 63. 63 web server ■vert.x core - very raw and basic HTTP server ■web server ext - neat path and content routing
- 64. 64 vertx.createHttpServer().requestHandler( req -> { LOG.info(String.format("Got request [%s]", req.path())); switch (req.path()) { case "/" : req.response().end("Ok. Here's root"); break; case "/other": req.response().end("Other things..."); break; default: req.response().setStatusCode(404).end("Unknown resource!"); } }).listen(port) vert.x core - very raw and basic HTTP server
- 66. 66 Router router = new RouterImpl(vertx); router.get("/users/:uid").handler( ctx -> { String id = ctx.request().getParam("uid"); JsonObject user = new JsonObject().put("id", id).put("name", "bartek"); ctx.response().end(user.encode()); }); HttpServer server = vertx.createHttpServer(); server.requestHandler(router::accept).listen(8080); web server ext - neat path and content routing
- 68. 68 //SessionHandler must be preceded with SessionHandler router.route().handler(CookieHandler.create()); router.route().handler( SessionHandler.create(LocalSessionStore.create(vertx))); router.get("/sessionCounter").handler(ctx -> { ctx.session().get("counter"); } web server ext - accessing session
- 70. ■adding EventBus via websockets ■using shared data S4c ■using web session ■adding REST endpoints ●GET /sessionCounter ●GET /globalCounter 70 let’s code! S4b/S4c
- 71. 71 The Big App
- 72. let’s create Jenkins Monitor ■fetching build statuses parallely ■storing build statuses in shared map ■serving builds list GET /jobs ■serving build status GET /job/id 72 let’s code! S5
- 73. 73 benchmarking
- 76. verticles: ■are actor-like ■can be addressed ■can subscribe to many addresses ■can do processing jobs ■can send back content ■can have multiple instances of same class 76 vert.x vs akka
- 78. vertically ■verticle can have multiple instances ■each instance can have own processor core horizontally ■clustering - lot’s of nodes ■eventbus reaches all nodes 78 how vert.x scales
- 79. polyglot 79
- 81. 81 puts "Ruby for the win!" eb = $vertx.event_bus() # Send a message every second $vertx.set_periodic(1000) { |v| puts "RUBY: sending Ruby message" eb.publish("producer.address", "Ruby shines!") } Ruby shines
- 82. 82 var eb = vertx.eventBus(); eb.consumer("producer.address", function (message) { console.log("JAVASCRIPT: Received a message: " + message.body()); }); console.log("Receiver ready!"); For JavaScript dare devils!
- 83. usecases 83
- 84. ■effective use of servers’ resources ■parallel computing ■great as a backend for lots of (mobile) clients ■nice integration platform ■could be awesome in microservices 84 usecases
- 87. grab a sticker! 87 YOU getting started
- 88. have fun! 88 YOU getting started
- 89. I’m not the owner of the pictures used. Just found them on: http://www.rantchic.com/wp-content/uploads/2013/12/Apollo-13.jpg http://www.gamesaktuell.de/screenshots/1280x1024/2009/04/terminator_2_blu_ray03.jpg http://tripoutlook.com/wp-content/uploads/2013/03/Car-parking.jpg http://upload.wikimedia.org/wikipedia/commons/5/52/Parallel_Parking_cars.jpg http://www.foreverbarcelona.com/wp-content/uploads/2014/02/Taxi-Tips.png http://www.125p.eu/wp-content/uploads/2009/03/fiat-125p-zmiennicy-5.jpg http://www.novosti.rs/upload/images/2011/07/2107/bg-taksi.jpg http://i.livescience.com/images/i/000/024/292/iFF/neurons-120208.jpg?1328727600 89 All the pics used
- 90. 90 Thank you