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.
So we have recently started moving algorithms to separate microservices from a large Eclipse RCP application (which by the way is tens of millions of lines of code - so we have our work cutout and it will take a long time). It would be great to drop by the conference and show you some of the design of software which we are using to deploy scalable scientific and engineering algorithms using cloud technologies like DCOS and Kubernetes backed by AWS and Azure.
JNoSQL is a framework and collection of tools that make integration between Java applications and NoSQL quick and easy—for developers as well as vendors. The API is easy to implement, so NoSQL vendors can quickly implement, test, and become compliant by themselves. And with its low learning curve and just a minimal set of artifacts, Java developers can start coding by worrying not about the complexity of specific NoSQL databases but only their core aspects (such as graph or document properties). Built with functional programming in mind, it leverages all the features of Java 8.
When the Eclipse Microprofile initiative was started in 2016, it only took about three months before version 1.0 was launched. From day one, there were four different implementations from four different vendors available.
And the progress does not stop there! Whereas version 1.0 was a subset of Java EE specifications, the following versions bring additional technologies useful for building microservices.
Current version contains APIs and implementations for:
During 20 years, we have been accustomed to Java EE (previously J2EE) managed by the Java Community Process. Not all of us were fully happy with this situation: we have often been frustrated by its slow process and its sometimes bloated specifications. But at least, it was considered as a long-term standard. In less than 6 months, everything has changed and now, we have Jakarta EE managed by the Eclipse Foundation. Who could have imagined such a change in a short period of time?
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
The latest version of Java's API for RESTful services has been released. With the open sourcing of Java EE to EE4J, the future of JAX-RS is wide open! In this session we will discuss what is new in JAX-RS 2.1 - reactive client, server sent events and more! We will look at actual code examples and some best practices. We will also discuss the future of JAX-RS in the EE4J community.
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.
Cloud native application development does rarely have the luxury to select one platform/runtime/language and often necessitates multiple technologies, e.g. serverless, reactive, MicroProfile, etc. How should organizations go about implementing cloud native applications based on all these technologies? Come and learn about the strengths and weaknesses of different cloud native technologies and how you can combine these without sacrificing efficiency, stability and scalability.
Conventional wisdom has it that Java EE is a bad starting point for building Java microservices, but conventional thinking isn’t relevant to the new wave of applications. It isn’t that Java EE isn’t a good choice (after all, most microservice frameworks build on parts of it); it’s that it hasn’t been growing fast enough to address the problems microservice architecture presents. Last year several Java EE server companies and Java user groups got together to start the MicroProfile initiative to help kick-start an effort to solve these new problems.
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.
“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.
With the right tools, building scalable applications can be much easier than it seems. Eclipse MicroProfile allows you to build such applications easily and you get a variety of options to scale them if you add distributed data grids. These can become a backbone for building horizontally scalable services, while at the same time providing flexible caching to scale up their performance vertically.
Microservices based architecture seems to be the common convergence point in the industry. But when it comes to security we are still struggling to evolve from monolithic systems or people oriented architecture.