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?
Microservices have become a prevalent architectural approach to developing applications. Moving from a monolithic application to multiple container-based services has many advantages. One of the largest is dynamic scalability; spinning up and shutting down instances of services to adapt to dynamic loads is very cost-effective in a public cloud environment.
For JVM-based applications, running in a managed environment using JIT compilation, this provides additional challenges. Primarily, this is around the time required for a service to warm up and reach the optimum level of performance. To address this, we have seen various approaches such as the Graal VM and Quarkus that use an AOT approach rather than JIT compilation.
In this session, we will explore the pros and cons of both approaches to help in understanding the tradeoff between initial performance and overall
performance. At the end of the session, you will have a clear idea of how to approach your Java microservice design from the AOT and JIT perspective.
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.
Microservice Architecture (MSA) is one of the recent trends in the area of Software Architecture. MSA promotes to decompose software systems into distributed services, each focusing on a well-defined, distinct task with the greatest possible independence in both technical and organizational hindsight.
Can it really be that easy?! Yes it can! Come check out this session where we'll discuss and demo how you can rapidly build data-driven microservices using GraphQL. MicroProfile GraphQL makes it simple to create Java-based GraphQL services with a few annotations. JPA makes it simple to access data in a database. When you put these two technologies together, sparks will fly (the good kind)! With very little code, we can build services that allow clients to get exactly what they want from the database.
In this talk we will follow a single rule to gradually discover the design principles at the root of most modular runtimes: OSGi, java modules, even microservices. We will contend that the degree to which a software system is committed to following this rule drives it's final shape in a way similar to natural evolution. We believe this will help software professionals understand why their modular applications exhibit certain traits like the particular distribution of complexity between modules.
Are you wondering how to secure microservices? Eclipse MicroProfile JWT (https://microprofile.io/) is the answer. MicroProfile JWT designs a token based authentication and authorization mechanism, which enables authorized access from clients to services or from services to services by using JWT token.
Microservices are often created by refactoring a service out of an existing monolithic application. There are some who suggest that for greenfield development it is actually preferable to build a monolith first and allow microservices to be pulled out as service boundaries are discovered. But whether you’re dealing with an existing Java-based monolith or are looking for ways to develop new functionality, the OSGi framework and Eclipse OSGi tooling can do a lot to improve your development process.
While microservice architecture has become extremely common, its use in the UI layer is still somewhat rare and difficult. Building microservices in the UI layer (sometimes called Micro Frontends) requires well-thought-out support frameworks that allow for collaboration between loosely coupled and independently deployable components. Well it turns out that the Eclipse Platform developers have been innovating and fine-tuning such frameworks for the last 20 years, and in this session we'll explore what they have to teach us.
Dive into the next generation cloud native framework for running Java in microservice oriented cloud platforms. Quarkus focuses on developers and ease of use in modern serverless environments.
It is a Kubernetes Native Java framework tailored for GraalVM and HotSpot, crafted from best-of-breed Java libraries and standards.
A hands on overview of the Quarkus cloud native framework, what it brings to the Java ecosystem and what new concepts and design guidelines it introduces.
