Cloud Native Technologies
How does one choose to architect a system that has a Microservice / REST API endpoints? There are many solutions out there. Some are better than others. Should state be held in a server side component, or externally? Generally we are told this is not a good practice for a Cloud Native system, when the 12-factor guidelines seem to be all about stateless containers, but is it?
Cloud Native Technologies
Jakarta EE 9 lowers the barriers of entry, eases migration, and lays a foundation for future innovation. Jakarta EE 9.1 takes this even further by offering Java SE 11 support.
In this session, I will go through what Jakarta EE 9.1 brings to the table and how this release lowers the barriers of entry, eases migration, and lays the foundation for a platform for future innovation. We will also look ahead to what future releases may bring.
The session includes a demo including converting from the javax. to jakarta. namespace as well as looking at available implementations.
Cloud Native Technologies
The new Jakarta EE Core Profile proposed for Jakarta EE 10 will enable smaller runtimes that are suitable for microservices to be certified as Jakarta EE compatible. The new profile will also aim to be an even better fit for compiling to native images.
Join this session for the latest updates of the progress with Jakarta EE Core Profile and Jakarta EE 10. Who knows, there may even be a demo.
Cloud Native Technologies
Security in Jakarta EE has long been under used and under specified. The existing set of specifications ranged from overly complex to non-existent. The result was almost nobody used standards for security. Java EE 8 changed that with JSR 375, the Java EE Security API. Its evolution Jakarta Security facilitates portable application security that integrates with container security. Allowing an application to provide authentication mechanisms like OAuth or OpenID Connect and that mechanism is treated just like built-in container mechanisms like FORM.
Cloud Native Technologies
The amount of data collected by applications nowadays is growing at a scary pace. Many of them need to handle billions of users generating and consuming data at an incredible speed. Maybe you are wondering how to create an application like this? What is required? What works best for your project? And do you need superpowers for it?
Cloud Native Technologies
This session will focus on some of the most widely used Jakarta EE features, demonstrating features via a series of examples. The examples used in the presentation will be representative of those which can be found in the "Jakarta EE Recipes" book, published by Apress.
Cloud Native Technologies
With the migration of the javax to jakarta package in Jakarta EE 9 and the support for the Java SE 11 runtime in Jakarta EE 9.1, the Java enterprise ecosystem, tooling and end-users have now a great opportunity cost to migrate or bootstrap Java Enterprise applications. This session covers code-driven recommendations and strategies to help you navigate the migration process towards Java cloud-native using Apache TomEE.
Cloud Native Technologies
Imagine that you're a Developer who's been asked to provision your Jakarta EE resources on Azure.
Join Rory, from the Microsoft Java Team, and learn how to create and build a Jakarta EE application on JBoss EAP for Azure App service.
We’ll cover:
- Starting your project with the Eclipse IDE and Jakarta EE Libraries
- Provisioning a database and connecting it to JBoss EAP via the JBoss CLI.
- Deploy your WAR and EAR applications using App Service’s deployment API’s or CI/CD integration.
- Set up auto-scaling to handle periods of higher load.
Cloud Native Technologies
Kubernetes is increasingly becoming the de facto standard to deploy not only Microservices or distributed applications, but any kind of runtime.
This means that as Java developers we have also an increasing responsibility to containerize our application and learn how to deploy it to a cluster. So now, we need to deal with and maintain additional resources such as Dockerfiles, Kubernetes configuration manifests, etc.
Cloud Native Technologies
Kubernetes has established itself as the industry standard for managing containers(and their lifecycles), but there is still not much content on the web about how to write applications that interact with Kubernetes APIs. If there is, it's mostly in GoLang. Since Kubernetes exposes most of its operations via REST API, all of this stuff can be easily done in Java using Fabric8 Kubernetes Client.
Cloud Native Technologies