The technical sessions of this track is filled with content covering everything you need to know about developing applications and cloud native microservices using Java. The topics include best practices, experiences, and recommendations using technologies and frameworks such as Eclipse Vert.x, Eclipse MicroProfile, and Jakarta EE as well as reactive programming, containers, and orchestration.
In reactive services is an essential that a request is not blocked anywhere during processing. Accessing databases is a tricky part here because there are currently not many databases providing reactive drivers. Come learn about Helidon Database Client - thin persistence layer in Helidon SE allowing working with relational and NoSQL databases the reactive way.
It's a challenge to choose Java microservices framework which satisfies your requirements. Some developers prefer reactive, functional style of APIs and other developers give preference to inversion of control, declarative style APIs offered by MicroProfile. In this session I will explain the differences and pros and cons of each approach. I will demonstrate how the functionality of MicroProfile APIs such as HealthCheck, Metrics and OpenTracing can be implemented in reactive-style applications.
With Microservices as its target, the programmer sees a gap between the typical old-school approach (deploying to an application server) and modern approaches.JAX-RS 2.2 allows to natively startup a web server, even in-process in an IDE, so it allows to simply start it as a Java main() method and debug its startup and requests processing just as easy as Hello World! No more slow build and deploy cycles! This talk demonstrates how to do that, and what more to expect from JAX-RS 2.2 and the further roadmap.
Creating cloud-native microservices is common, but which programming model to choose from.
At the moment, MicroProfile and Spring are two popular programming models for developing microservices. What are the differences or commonalities between them?
This session is to focus on comparing the two programming model side by side. If you are Spring developer, after this session, you should be able to grasp MicroProfile very quickly and vice versa.
Have you ever wondered what is the modern way to create cloud-native microservices? Is the microservice you have created good for cloud infrastructure? How best to utlise the modern technology to improve your efficiency, so that you can just focus on business logic?
In our session we will run through the way customers are using Jemo in the real world. We have also reached out to some of the user base should be able to have an actual customer speak alongside the project lead (Christopher Stura) to talk about what Jemo has done for their business.
We will then throughout the talk connect the dots between the areas of technological innovation addressed by the Jemo project and how those tech features have enabled customers to achieve real business value.
How can you make different pieces of your unit of work consistent in the distributed setup of your micro-service application?
You associate the term transaction probably with a database, but the data source can be anything including a database in the micro-service world.
The MicroProfile Long Running Actions specification is based on sagas and the OASIS LRA transaction model specification. It defines the framework to guarantee the eventual consistency requirement using compensating actions for example.
- Intro to problems around distributed systems and microservices
- stateless protocols and designs - implications and drawbacks
- Kubernetes and scaling - application behavior and challenges
- How Akka Cluster solves the challenges and drawbacks
- Demo on Minishift (Scaling PODs and visualize how Akka Cluster reacts to infrastructure changes without manual intervention)