Ever wondered what makes a cloud-native application "cloud-native"? Ever wondered what the unique challenges are and how best to address them on fully-open Java technologies? In this workshop, you'll learn what it means to be cloud-native and how that impacts application development. You'll learn about Eclipse MicroProfile, an industry collaboration defining technologies for the development and management of cloud-native microservices.
The OpenAPI Specification (formally known as Swagger) describes APIs in a way that is standardized, machine-readable, and programming language-agnostic. It is an open source project hosted by the Linux Foundation.
There have been many announcements regarding frameworks or tools supporting this standard: For example, Eclipse MicroProfile 1.3 provides a set of annotations that can be used on top of JAX-RS, and version 3.5.2 of Eclipse Vert.x provides automatic requests validation.
Containers, Kubernetes, Cloud Native, Microservices, Eclipse MicroProfile. It feels like you’re going to drown amongst the buzzwords! In this session we will guide the developer through the minefield of all these buzzwords to understand the concepts and develop solutions with them.
What if there was a way you could take advantage of the latest microservice architectures by leveraging the developers and skills you already have?!? In this session we’ll show you how with Eclipse MicroProfile and Red Hat’s implementation Thorntail. We discuss all the cool features it allows you to easily use, such as OpenTracing, Metrics, and layout the current roadmap plans. Then we move onto a demo that showcases what’s possible with Eclipse MicroProfile, utilizing the existing specifications, built with Thorntail.
The craze is fully on. The past couple of years have seem micro services grow from next _flava_ to fully consuming of the software industry. The Eclipse micorprofile.io project is tackling the issue putting common usage patterns together over a foundation of CDI. What better assembly driver is there than OSGi to put it all together. This talk will demonstrate building your own MicroProfile using OSGi and the OSGi enRoute packaging model.
In this talk we will walk through MicroProfile-OpenTracing project and explain how it can improve observability in your cloud native Java deployments. At the beginning there will be an introduction to distributed tracing and then we will continue with the project specific features. We will also touch more advanced topics like tracing in (Istio) service mesh architectures, distributed context propagation and best practices when instrumenting your business logic. Last but not least we will talk about project roadmap and how to get involved.
To develop a cloud ready application is only one side of a medal, the other side is the cloud environment hosting this application. As a software architect you have to make some decisions giving a consideration to your target runtime environment. Some aspects like configuration, fault tolerance, health checks, application metrics, request tracing and service discovery have a strong coupling with the cloud environment. Eclipse MicroProfile has a lot of specifications to make your Jakarta EE based application ready for the cloud.
MicroProfile is well established as a microservices development platform. It blazed the trail for the Jakarta EE movement. In it's short tenure, MicroProfile has introduced us to the Fault Tolerance, JWT Propagation, Metrics, Rest Client, Config, Health Check, OpenAPI, and OpenTracing programming models. But, what's next for these two key Eclipse projects? Will MicroProfile stay independent and continue to demonstrate it's fast-paced innovation? Or, will it be combined with Jakarta EE, which is also promising a faster development cycle than the previous Java EE platform?
Experience MicroProfile and Java EE firsthand with Liberty Bikes: the four player, elimination game built using the latest technologies of Java EE 8 and Microprofile 1.3. You've seen the Java EE charts. You've seen the lists of technologies. You've probably even heard how you can write 12-factor apps using these technologies. Come to this session to see the actual code and how to leverage those technologies in a simple, practical manner.
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?