Download to read offline
Uploaded byBert Jan Schrijver
Vert.x NL meetup October 2017 - Building microservices with Vert.x
Vert.x is a toolkit for building reactive applications on the Java Virtual Machine (JVM). It is used by Malmberg, an educational publisher in the Netherlands, to build scalable e-learning applications using microservices. Vert.x is event-driven, non-blocking, and supports multiple programming languages. It allows building distributed applications where verticles (components) communicate through an event bus. Vert.x is well-suited for microservices due to its lightweight verticles that can be developed, deployed, and scaled independently.
Vert.x NL meetup October 2017 - Building microservices with Vert.x
- 1. Building microservices withVert.x Bert Jan Schrijver @bjschrijverbertjan@openvalue.nl
- 2. @bjschrijver Let’s meet Bert JanSchrijver
- 3. @bjschrijver Outline • Background • WhyVert.x? • Basic demo • Deep dive • Advanced demo • Microservices with Vert.x • Vert.x in practice
- 4. @bjschrijver Background •Introduction •Why Vert.x? •Basic demo •Deepdive •Advanced demo •Microservices with Vert.x •Vert.x in practice Malmberg is an educational publisher in the Netherlands. Malmberg is building modern, rich and scalable e-learning applications using Java 8, Vert.x, AngularJS and MongoDB, running on Amazon cloud services.
- 5.
- 6. @bjschrijver Vert.x: the basics •Toolkit for building reactive applications on the JVM • General purpose application framework • Swiss army knife for building modern and scalable web apps • Event-driven, non-blocking • Polyglot • Lightweight and fast • Fun to work with!
- 7. @bjschrijver Why did wechoose Vert.x? • We love open source • Powerful module system • Reactive characteristics
- 8.
- 9.
- 10.
- 11. @bjschrijver Vert.x in depth •Event driven and non blocking event loop • Multi-reactor pattern
- 12.
- 13.
- 14. @bjschrijver Vert.x in depth •Event driven and non blocking event loop • Multi-reactor pattern • Actor-like concurrency • Management and monitoring built-in • Distributed event bus
- 15. @bjschrijver Vert.x’s golden rule •Never ever ever block the event loop! • Need to do blocking stuff? Use a worker
- 16. @bjschrijver Vert.x event bus •Both request/response and publish/subscribe • All Vert.x instances have access to the event bus • Verticles interact using messages • Messages are received by Handlers
- 17. @bjschrijver Vert.x in depth •Verticle, application, instance, JVM: Host JVM Vert.x instance Verticle Event Bus Verticle Verticle Verticle JVM Vert.x instance Verticle Verticle Verticle Verticle
- 18. @bjschrijver Vert.x in depth •Verticle, application, instance, JVM: HostHost JVM Vert.x instance Verticle Event Bus Verticle Verticle Verticle JVM Vert.x instance Verticle Verticle Verticle Verticle
- 19. @bjschrijver Vert.x in oneslide Source: http://www.slideshare.net/clement.escoffier/vertx-31-be-reactive-on-the-jvm-but-not-only-in-java
- 20.
- 21.
- 22. @bjschrijver Anatomy of amicroservice • Small in size, single responsibility • Runs in its own process • Independently develop, deploy, upgrade, scale • Has its own data store • Distributed by default • Potentially heterogeneous/polyglot • Light-weight communication
- 23. @bjschrijver Anatomy of amicroservice • Small in size, single responsibility • Runs in its own process • Independently develop, deploy, upgrade, scale • Has its own data store • Distributed by default • Potentially heterogeneous/polyglot • Light-weight communication microserviceVert.x module
- 24.
- 25. @bjschrijver 4 years ofVert.x: situation • Organisation structure: • Core platform team (infrastructure) • Core modules team (Vert.x modules) • Product teams • Deployment model: AWS, Nginx, MongoDB • A product consists of multiple lightweight artifacts • Re-use of Vert.x modules (no central services)
- 26. @bjschrijver 4 years ofVert.x: deployments • Rolled our own deployment tooling and open sourced it (https://github.com/msoute/vertx-deploy-tools) • Controlled from Jenkins • Zero-downtime deployments • Microservice deployments
- 27. @bjschrijver 4 years ofVert.x: experiences • Very suitable for test driven development • Integration tests with embedded MongoDB • Good cooperation from the Vert.x team • The Vert.x community is awesome!
- 28. @bjschrijver 4 years ofVert.x: challenges • Callback hell • Java 8 helped a LOT • Rx fixes the remaining issues • Blocking the event loop • Scaling / JVM overhead • Debugging • Static code analysis • Upgrade from Vert.x 2 to Vert.x 3
- 29.
- 30. @bjschrijver Summary • Vert.x: toolkitfor reactive applications on the JVM • Polyglot, distributed, event-driven • Very suitable for building microservices
- 31. @bjschrijver Resources • https://github.com/bertjan/vertx3-examples • http://vertx.io •http://vertx.io/blog/my-first-vert-x-3-application • https://github.com/vert-x3/vertx-examples • http://github.com/msoute/vertx-deploy-tools Don’t worry, I’ll tweet a link to the slide deck ;-)
- 32.
- 33. @bjschrijver Summary • Vert.x: toolkitfor reactive applications on the JVM • Polyglot, event-driven • Very suitable for building microservices More info: http://www.slideshare.net/BertJanSchrijver/devoxx-be-2016-how-to-build-your-own-selfdriving-car
- 34.
- 35. Thanks for yourtime. Got feedback? Tweet it! All pictures belong to their respective authors @bjschrijver