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.
Organizations have complex application environments that include multiple deployment infrastructures, tools, languages, and frameworks, making task, tool and training management a challenge. Having a robust, flexible, future-proof unified application environment in which existing and new applications operate and function across highly-distributed platform is essential.
In this session, hear how containers are changing the way developers code, test, and deliver solutions. Learn about techniques being designed that will help reduce the knowledge burden and that are beginning to provide dev environments more suitable to the world of cloud native. From new platforms such as Knative and Jenkins X through event-based application architectures to new open source dev tools like Eclipse CodeWind, j
ust writing code is here to stay.
You're given the task of writing a microservice AND providing a documentation in OpenAPI format. You already know that there are two main approaches:
- design-first : write the OpenAPI document (a.k.a. the
openapi.yaml file) and then generate the code
- code-first : write the code, using OpenAPI annotations, and then generate the OpenAPI document
Which approach do you choose?
I'll compare the two approaches by showing a simple Java microservice implemented twice, once design-first and once code-first.
This talk provides an overview and a state of the nation for JVM directions from a Cloud perspective
Liberty Bikes is a four player, elimination game built using the latest technologies of Java EE 8 and MicroProfile 3.0. Come build your first (or 100th) microservice as you create an AI to compete in a battle royale against your fellow attendees. In this lab, you will develop a complete microservice, leveraging MicroProfile Rest Client to seamlessly integrate and communicate with an existing application. Can you become champion of the grid?
The target audience are Software Engineers and Architects that have a basic understanding of Java, containers and the cloud and are keen of sustainability.
I will take a very simple example Java application and demonstrate how it can be refactored to adhere to cloud native principles. Thereby, I will focus on aspects that are relevant for making the application more sustainable: More flexible usage of resources.
Eclipse MicroProfile is a collection of community-driven open source specifications that define an enterprise Java microservices platform. The open source approach of MicroProfile removes reliance on any single vendor’s release cycles and makes the development of microservices a natural extension of Java EE developers existing skill sets.
Eclipse MicroProfile provides specifications for the most commonly used microservice patterns. This session presents a group of patterns that will be in explained and demoed live in a down-to-earth and easily understandable way.
Patterns covered include Service per Container, Externalized Configuration, Health Check API, Application Metrics, Circuit Breaker, Access Token, Distributed Tracing.
There will be live coding and demo of all technologies implementing the patterns.
1. Jakarta EE Apps and Micro profile
2. Legacy container booting style vs. Microservices
3. Micro profile for real enterprise systems - real-time and batch
4. Faster boot-up for "cloud-native" financial systems
5. Streaming architecture with microservices
The technology landscape is changing at an ever-accelerating speed, and established financial institutions are facing stiff competition from FinTech startups. Rigid architectures, based around risk-avoidance, become a blocker to innovation, where small agile operations can try new things without remorse. Users have gotten accustomed to always-available, instant services, where processing in daily or monthly batches just don't cut it anymore.