Jakarta EE’s programming model and application server runtimes are a modern approach for developing Java-based enterprise applications. Especially when complemented with Eclipse MicroProfile and supporting tools, these fit perfectly in containers and scalable infrastructures. In this talk, I will explain how to tailor and optimise such enterprise applications to the max in order to achieve optimal value and development experience. In addition, I will compare some key concepts with competitors like Spring Framework.
Eclipse MicroProfile provides a set of APIs for creating cloud-native microservices. In this session, I will start with a blank sheet and build a set of well documented, configurable microservices that communicates with each other in a secure, traceable and fault-tolerant way using implementations from a wide range of vendors.
You will get an overview of the technologies and learn how to get started with Eclipse MicroProfile to create portable 12-factor microservices in an efficient manner.
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?
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
Kubernetes is becoming the de-facto platform to deploy our application nowadays. But this movement also implied some changes on the way we code our applications, where we just develop a monolith application where everything was up and running up front, now we are breaking down this monolith into (micro)services architecture. Although it might seem easy, done properly is not an easy movement as there are some challenges to address that were not there before, at monolith architecture time.
This tutorial explains how to design applications to effectively develop them with the Microservices architecture. It examines building microservices step by step, how to design boundaries between components using Domain-driven design and when to split a microservice into smaller services.
This live coding session shows how to design Jakarta EE applications to effectively develop them with the Microservices architecture. From a simple Jakarta EE service, we'll evolve our code using MicroProfile to build a scalable system with very few code changes and no code waste.
You'll see how to focus on business logic and application design, and not to worry about the technology or cloud. With Jakarta EE and MicroProfile, it's very easy to evolve your codebase to scale it and run in the cloud in the future.
Why reactive? How is MicroProfile related to reactive programming? There are many reactive Java libraries but they all work in a different way and provide different API. MicroProfile brings common reactive APIs that can be reused in many libraries to provide a unified experience for many Java developers. Including reactive operators, messaging, REST and more.
Jakarta EE with MicroProfile is the platform of choice for building applications for private and public clouds. The nature of microservice architectures allows significant design and architectural shortcuts. The code reduction increases the productivity and shrinks the codebase at the same time. In this session, I'm going to code a few microservices "from scratch" and explain the design choices on-the-go.
Attendee's questions are highly welcome.