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.
MicroProfile, RxJava, React.js - what else do you need to build lightweight but robust reactive systems efficiently with opensource tools? Maybe something for effective data processing and distributed persistence? You can have it too with Kafka and Hazelcast. Now let’s have a look at how to assemble all together in almost no time, using Payara Micro.
On my right : Java 9 and its modular approach with JPMS (also known as Jigsaw).
On my left : the Micrroprofile platrform which targets very small deployment to perform small feature in the most resilient and lightest way possible.
Can we marry both ?
In this session we'll explore all the challenges to solve to use JPMS on microservice and explore some solution to get started with modularity and Microprofile.
In a second part we'll try to creaate a full modular standalone runtime image with Jlink, and, who knows, perhaps we'll succeed?
Microprofile is a great standard to build vendor neutral micro services. One of the nicest feature of the platform is probably the fact that it is CDI centric.
Having CDI as a core requirement for Microprofile allow users to add features to their micro services in a standard portable way.
In this session we'll see how we can use CDI to add extra features to a microservice in a natural and portable way. We'll start with an existing extension and then we'll create our own CDI feature by using protable extensions to show how easy it is to extend the Microprofile platform
Lifting and shifting existing applications to the Cloud is a common task for many deveopers these days. This session will explain 3 common scenarios for moving Java EE standards based applications to Azure using concepts applicable to other cloud environments as well. One is of course using Containers and Kubernetes; Second is by using a platform runtime such as Azure AppService. And the third is by using Service Fabric. In the end, we will see the differences, pros/cons, and also open for Q&A.
On March 2018, Microsoft released the source code of one of its core Azure services: Service Fabric is now open sourced on GitHub - https://github.com/Microsoft/service-fabric/. This talk will introduce Java developers to the platform: how to download and install Service Fabric on Linux, and how to run an application designed for it.
Java EE, cloud native and service meshes — this doesn’t really sound like a good fit. Or does it? Is it possible to develop modern, cloud native Java Enterprise applications that fulfill concerns such as scalability, monitoring, tracing, or routing — without implementing everything ourselves? And if so, how to do this?
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?
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:
Exposing APIs has become an essential aspect of all modern applications and services. For both the clients and providers of these services to properly communicate there needs to be a clear, complete, and concise contract. And, the definition of this contract has to be easy. The OpenAPI v3 specification (https://www.openapis.org/) is the standard for RESTful services. And, the Open API component of the Eclipse MicroProfile project defines the Java interfaces and annotations necessary to natively produce OpenAPI v3 documents from JAX-