Writing microservices might be easy. What is the best practice for writing one? Your microservice needs to be configurable, resilient, etc. Come to this session to learn the best practises of building microservices.
MicroServices, MicroProfile, EE4J, & Java EE
Planning to build microservices? The best practice of building a first-class microservice is to follow 12-Factor app. But how to fulfill the 12-factor app rules, e.g. how to achieve externalise the configuration, fault tolerance, etc? Come to this session to build a 12-factor microservice using MicroProfile programming mode in half an hour with live code demo.
MicroProfile defines Config, Fault Tolerance, Health Check, Metrics, Open Tracing, Open API, JWT security, etc, while Istio has Fault Tolerance, Tracing, etc. Will they conflict to each other? Come to this session to find out the work being planned to build an ecosystem for MicroProfile and Istio and how to make MicroProfile-based microservices the best performed microservices in Istio.
Already we can see and feel that the development of "Java EE" after the contribution to Eclipse will be different from the past. We are seeing enthusiasm and participation from the various teams at an all-time high! But, what will be different after these contributions to EE4J (Eclipse Enterprise for Java) is complete? Come to this session to learn what's changing, besides just the name... :-) I will give you an overview of the projects already transferred and what projects are left. I will also give an overview of the new and updated processes, as well as what processes still need so
“Sorry, you cannot withdraw any money, because the security service is temporarily unavailable. Kind Regards, your ATM.”
In microservice architectures, latency and system failure are added risks. How do we architect our system that it can cope well with erroneous situations and prevent the authentication service become a bottleneck? This session walks you through the concept of token based security and explains how to design a scalable and fault-tolerant security system using the Microprofile JWT-Auth with an identity and access management solution.
What does it take to build service oriented applications running in the cloud? This session introduces you to 5 essential Microprofile API’s that address security, configuration, fault-tolerance, remote communication and monitoring. We take a high level view and explore the architectural purposes of the API’s and discuss where and why these API’s fit in cloud-native applications, backed by code examples that demonstrate the application level usage.
How to build configurable, resilient, monitorable Java Microservices? Eclipse MicroProfile (https://microprofile.io/) is the answer. Eclipse MicroProfile has rapidly become a rich set of technologies essential for writing configurable, fault tolerant, secure and production-ready Java Microservices.
Java EE is currently going through its biggest change in a decade as it moves to the Eclipse open source foundation under the EE4J top-level project. When this succeeds it will accelerate the enterprise platform's evolution towards microservices through the work started in the Eclipse MicroProfile just over a year ago. The MicroProfile initiative was formed to inject new pace and innovation into the enterprise Java landscape and is having the desired impact.
Monoliths aren't bad in all situations, but in larger projects, it is desirable to work in a more modular way.
But micro-services bring a lot of complexity which is maybe not always desired or needed.
Self-contained Systems, which are autonomous web applications, are an ideal way to make your large application manageable by multiple teams.
This session will make a comparison between the 3 architectural styles, monoliths, micro-services and Self Contained Systems highlighting their strengths and their weaknesses.
With the rise of micro-services, REST communication is more popular than ever. But the communication between the different parts must also be performed in a secure way.
First, we need to know if the user or system is allowed to call the JAX-RS endpoint. For this authentication part, self-contained tokens are the best option to not overload any of our services in the system. JWT which contains the authentication but also can contain the authorization info is ideal for this use-case.