On the right corner, Quarkus, goes into his challenge against Micronaut the lightweight champion, and pound-for-pound with Spring Boot the best microservice framework in the world. Who will win the world “Cloud Native Java Runtime” title fight?
In this 3h long workshop you will bring your own laptop, install all the needed tools and be ready to develop from scratch three microservices: one written with Quarkus, one with Spring Boot and one with Micronaut. Add some business logic, access a database in a reactive and imperative manner, run them on HotSpot, compile them with GraalVM, containerize them with Docker and deploy them to the cloud. Then, add some load testing, scale and monitor them. At the end of this workshop you will know which of these microservices is the most appropriate in terms of performance, resource consumption, and startup time… or maybe you won’t ;o)
For this workshop you will need to install:
- Java 11, Java 17 and GraalVM
- Your own IDE
- Docker desktop
- An HTTP client (cUrl, wget, Postman)
- Have a Docker Hub account
- Have a GitHub account
- Have an Azure account (we will give you some credits)
Design patterns for building distributed, resilient, and scalable web applications are well known today. However, setting up a project organization to build them effectively remains a challenge, especially when the team itself is distributed. The "human" factor is a source of problems that are difficult to predict.
What would happen if you could take inspiration from the architecture of your applications to improve the communication of your teams?
Microservices, messages queues, load balancers, caches, sharding, decoupling... These architectural concepts are designed to improve digital exchanges within our apps, and above all to anticipate and manage failures. By modeling the exchanges within your team as software architecture, we will see how these design patterns can also be effective in solving our communication issues, very human this time.
You've probably seen these new smartphones with foldable screens, like the Samsung Galaxy Fold, or with two screens like the Surface Duo. They're already on the market, so it's up to you to update and rethink your web apps for these devices! But how? Where to start? Fortunately, the web is constantly evolving and has already started adapting for these new devices, thanks to new APIs.