Jakarta EE JakartaOne Livestream 2022, 15 Dec 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Deep Dive: Microprofile 6.0 - JakartaOne 2022

Description

Jakarta EE 10 Core Profile was the new profile in Jakarta EE 10. One of the reasons of creating this new profile was for MicroProfile to adopt Jakarta EE much easier. The new shining hot-in-the-press MicroProfile 6.0 has already fully embraced Jakarta EE 10 Core Profile. Apart from this, MicroProfile 6.0 also provided some major updates from MicroProfile Metrics, which enabled the adoption of Micrometer and MicroProfile Telemetry that consumed OpenTelemetry. Come to this session to learn all about MicroProfile 6.0 with a live demo on Open Liberty.

-

Jakarta EE gives developers a comprehensive set of vendor-neutral, open specifications that are used for developing modern, cloud native Java applications from the ground up. With Jakarta EE, technology developers and consumers can be confident they have the best technologies for developing cloud native, mission-critical applications. And they can build on decades of Java developer expertise to move existing workloads to the cloud.

Learn more: https://jakarta.ee/

Follow us on Twitter: https://twitter.com/home
Follow us on LinkedIn: https://www.linkedin.com/showcase/jakartaee/
Like us on Facebook: https://www.facebook.com/JakartaEE/

A

A

I am Emery Jones from IBM I'm, Java champion and I'm, also Cloud native architect and I'll Kate like for Liberty and I, spend the most of my time, working on macro profile to have a year and their implementation in open Liberty. So in this talk, I'm going to do a deep dive into micro profile, 6 and oh, as you have mentioned, have you seen if you have attended a few talks earlier?

A

You know also with some other being mentioned, that micro profile metrics, the 5.0, the the customer scope and the en briefly talking about micropro Classics. So what's your micropro Classics. So in this presentation, I'll give you a quick overview about microprofile Canada, the current status and also with we spend the most time talk about the 6.0 and with a few demos, and then we pick into the future micro profile, like especially in like a next year. 2023.

A

This year and micro profile working group growing, so it's uh thank you. Microsoft and I'm prampton join the micro profile working group. So now we have like a 10 working group members and also we are trying to grow the community as well. So what is the space so? And at this moment I got? The micro profile has like has um platform release and also Standalone release. The platform really is. Obviously the current release has a few technology Technologies, plus these eight specifications and also there's a few uh Standalone release for the reactive stream operators.

A

Reactive messaging contact, propagation, graphql Ria, so they are separated from the platform release.

A

For the implementation of microphone profile, this is the micro profile was mentioned frequently in today's Decatur. One live stream, so, as you can see, a lot of like the local product already implement the macro profile in IBM like the open, Liberty, open source project, also ibms website Liberty, basically repackage the open, Liberty and also added a few other features. Red hat is a world of fly.

A

Gboards, EAP and qualcus Tommy driver has a patch Tommy Oracle has the halogen, and also some operana, and also priora, and also Prana cloud and Apache Geronimo producers, Apache launcher, and also some others like hammock. As you can see, it's like a very wide range enjoy the implementation. So that's. Why so why this standard matters, because the API is like adopted by a lot of implementations now with that, like a discussed, was here in micro profile 6..

A

So what I'm going to present in that in the following few slides is about what we have agreed in the release plan and a ballot is the ongoing. Hopefully we can conclude the micropriatic system.

A

So this is the plan for the micro profile, 6 Yen. Also, a demonstration in his talk, basically micro profile 6, will adopt like article E10 code profile from the very beginning from the micro profile window. All release is a macro profile package is back, so it's from a micro profile. 6 the oil is a package 10 core profile and plus it is like the eight micro profile specifications.

A

uh As you can see, the kind of the updated specifications of open, API, 3.1, GWT, authentication, 2.1 on The Matrix and you can see the yellow one and the new one is called micro profile Telemetry. So this is the news back. It is replaced the micro profile open 3G. You can see the open Tracy move with the to the Standalone, so it's a because it's no longer strategic, as you can see so I will discuss like a later about the micro profile. Telemetry.

A

So, what's in the micro profile, open, APS 3.1, so the the thing I want to, let you know, is um open. Aps reader-wise has no background incompatible changes. So it's a so that's why the manual release. So it's uh what's in the what's in this video one is the first thing we have been putting on the agenda. We want to integrate closely with the Cuttery Technologies.

A

One thing is the beam validation so in the past, even if you use beam validation, you have to specify the open API like apis, like annotations, to be able to honor the like some descriptions and from the micro profile. Open API is 3.1 like it automatically translates being validation like annotations, such as positive automatically. Give you some more like. The description you can see see is the minimum minimum zero.

A

The other thing is um security requirements set a set is the kind of the kind you use can be used to model, both um optional authentication and multiple authentication. So in this flavors I mean the optional user, so either one is the empty here and this flavor, you have a Open Bracket, and here you contain both. So this is kind of the the multiple.

A

uh The third one is that there's no properties added to schemas is here. When you describe the schema, you can see additional properties and then we will generate when you like. uh Do the um open API. So, basically, you can see the additional properties you can see the the ref to the another clause.

A

The following thing is the API responses. Like the API response, this annotation can be added to the class like level in the past. You have to go to the method so which this means this response applicable for all this methods, foreign.

A

Extension name value, and then we will generate this description. You can see. This is a like a name on the value automatically being like owners. So that's a quicker runs through about micro profile, open API, 3.1. The next thing is the micro profile. Gwt201 again, the DWT 2.1 is the is the manual release. Is there's the kind of no backward incompatible change.

A

So the first thing is that you can like specify the GWT token age. So basically, in the micro profile, configure Source, you can say mp.dwtw verify.2.h, so this is in second, so you can I think it's kind of the is the runtime with the implementation will really and validate the jwc token to see whether it's still valid or not.

A

Okay, the the second one is the another property added to like specify the clock screw. So basically again, this is second against kind of the within this 60. Second, the token won't be expired, so it's this indicator for the different computers they use a different like they might have a different time, but it's a kind of the dedicated for some cookie, like some token expires, just because the computer time different.

A

Algorithm, so basically it's the conspiracy if I was allowed the algorithm, so you can say okay, this is the. This is the only this. This um like the algorithm is allowed to deprecate so they're the same people.

A

Observation all these kind of the survey and Etc job wizard, gradually kind of feel in the background, is no longer like a mainstream. It seems, like macrometer, is kind of as a library picked up more kind of popularity and also with the spring. Also adoption uh like a macrometer. So there's a saying: why? Don't we just throw away macro problematics adopt some strategy? Libraries. The reason is um because there's some current micro profile customers Etc. They prefer like the Simplicity or micro profile metrics.

A

So that's why it's a micro profile, metrics group continues trying to incorporate, like some other more popular Technologies, such as macrometer and also like um still offer some apis to the end users, so so that they do not need to learn that another Library. So basically, they can still use relay on the micro profile metrics and the uses that, like the apis, they understand or annotations. They don't need to have to plug in the extra libraries and understand all the how to use them.

A

So this is the main purpose why the micro profile metrics is still evolving. So it's um let me take you through and what's in micro profile, Matrix, the 5.0 and also I will do a demo as well.

A

So your micro profile 5.0, is to continue to provide a micro, parametrics API again, if you know macro profile, metrics, it's a added some like as annotations. Basically so you can directly use it or you can use it programmatically, so it's some there's some apis as well, and then with that, your application is possible among the micro profile, metrics implementations.

A

uh The second one is now you support multi-dimensional Matrix, so this is kind of the good feature, um inspiration from macrometer as well. So you can see here like um how did the customer scope was created? Was it supported? So you can see here you can see okay, the driver and also you can see the scope. So this is the kind of the customer scope you can provide your own scope and then later on, you can query query that the the following way is um basically is.

A

This: is the kind of unbeans session he's very excited for this customer scope support so from now from macro profile, metrics 5.0? It offers customer scope. So basically, if you you are the developer, you added your own scope and then you can do a particular URL. You can directly see uh I mean the metrics. You add it, so this is the. This is really neat.

A

Finally, uh I mentioned earlier micro profile. Metrics is kind of provide your upstreet abstraction, like the client facing uh like a interface, so basically the behind the scene. The implementation you can choose whatever like you like, you could choose the micrometer as an implementation or you could choose like some other implementation, such as the open, Telemetry, Matrix and Etc.

A

So let's have a look at the micrometer micrometer is um uh developed by Spring like it provides a simple facade. So basically a lot of monitoring system like can plug in and provide the instrumentation. So it's a it's the most, it's more like a sl4g. Another thing is kind of the uh like the Implement instrumentation, the they can plug in all the implementations and Etc, and then you can stream out this Matrix. So so that's the micrometer, so the other, like the Technologies called open, Telemetry open Telemetry, is under cncf. It is back.

A

It's a language agnostic, so this is the like a different flavors, the other Java there's some other languages. I just mainly talk about Java in the in the open, Telemetry Java product. uh Like it's a kind of trying to implement the open, Telemetry specification, it offers like a Java API. It offers the SDK and it has some instrumentation as well and I, also like how tracing it has a Java agent support. So it's um the other thing.

A

I want to mention open, Telemetry the trans room like a cover, all the telemetrios deck, so it's including Matrix, logging and tracing. This is um so basically it's the one pillar here um like in the in a contact without the open television Matrix.

A

So you can use the open header picture a Java like a like the implementation trying to do some a micro profile metrics by the oh.

A

So in the micro profile 5.0, you continue to have the slash Matrix and the point, and the data is written from like a slash, Matrix core in the Prometheus 0 to 0.4, uh like the format, another implementation, you can also support your open, Matrix format. So it's uh again, it's a slash Matrix to give you all the metrics, all the registry metrics and then, like previously, you have a slash Matrix slash base, give you the base, Matrix all strategy, Matrix, slash vendor, give you the vendor Matrix.

A

Similarly slash Matrix, slash application, so give you the the application, give you the application Matrix. Now the change is in order to support a customer scope. You know it will be very difficult to use this large metric system strategy, something else so with that or basically the team, like um this, this class among themselves and then eventually come up with is a new format. It's slash magic question.

A

Mask scope equals so scope equals the base, give you base Matrix and vendor and application, and also your customer scope, and you will get your customer scope all these metrics and then you can even go to more details. You can even just say: okay, what is the metric name, so you can do a question mask scoping course and then name it course to get that particular Matrix match this query.

A

A

Metrics under the feature MP Matrix, the dash 5.0, so it's obviously we kind of provide like Avenger Matrix, give you a loss or gdm all these some metrics data, and also we obviously support the microphobia Matrix the API um and also like it goes without staying. We add the customer school and Etc and in our implementation we put in micrometer, so it's a in without actually either like.

A

um Also, you can expand it to plug in your own. Like monitoring system like like a Autobox, you have a Prometheus meteor registry and also you can plug in the elastic meter registry, a New Relic or denotes meter registry and Etc. It's a very kind of flexible people and it works with many kind of monitoring systems, and so, as you can see, from the slides, the the kind of more than 30..

A

So in the next few, slides I want to like give you a quick overview about micro profile, magic survival, because it's um it is, it has contained backward incompatible changes because it's because it's previously based on job wizard now is allow macro meter to be able to implement it. So it's some apis. It has changed, as you can see, the red red ones means this has been removed, yellow marked, yellow means, modified and blue means new.

A

So from now on simply um times and concurrent gauge or meter, this annotation has been removed and their corresponding metric classes being removed and a gauge and counterametric timer has been like modified like yeah, so in the next slide like in this slide, as you can see, registry type being removed, but whoever is additional registry, a scope and then also the um the magical.

A

Basically magical registry has been updated and also the metadata has been updated as well, and the snapshot is updated is a better suit suit, micrometer model and percentile value be created. So it's a better to see the older percentage like a data data point foreign.

A

So with that I'm going to do a quick demo about some micro profile, metrics.

A

A

Emi, uh like the vs code, like I, have the macro profile metrics, the 5.0 feature enabled so at first I just uh show you like I, have a car Matrix. So basically in this one I want to also demonstrate to you here here. How do you add the like uh a customer scope, so you can just say ready to scope. This is your customer scope, so you can like inject the magic registry. So this is another thing I want to mention.

A

Is that, as you can see here in the background, macrometer is working, however, I don't need to use any micrometer apis directly, I don't have to register a meter registry, create a global registry like and do my own like a Registries and then schedule is a micrometer. So this is the implementation automatically implementation of micro profile, metrics I automatically. You do it for you, so you have created this customer scope and the Creator is basically metric registry I've been injecting into it, and then you can like create a gauge.

A

You can see card or log to gauge and speed, and then you can even do the kind of the metadata Builder here. You can build the Cosby's summary metadata and later on. You can add this uh history program.

A

So here again you can register a timer, so you have like these Matrix catalog, the speed Carlos vegan sbm, like a summary, and also you have a timer and uh in this application is very simple: it's like a jux AS application, so you create like the metric like the car Matrix, to continue all these metrics and in this like a Jacks as resources, uh and uh basically you can. Basically you can inject this car Matrix.

A

So it's here you can inject this cometric scene to your controller uh and then there's a few uh like uh like operation rest operation to to the log analog and then started driving. So basically it's the simulator here is Simulator the speed, so basically things that started driving and then under driving. So it's a starter stop.

A

So it's a major like a simulation is the status speech, kind of thread here and and basically randomly generally just speak as the speed, and then this is called The Matrix, so speed Updates this last video updated directly going here. So basically, this is like your histogram. So it's basically uh have the tag and also the value and updated speed. So it's um uh I have this application like running already, so it's um so it's in here.

A

So in this basically the this is the application running, so it can see, stop driving is already driving. uh So basically, if I directly go to the like this, the the graph anal dashboard. So basically here is the uh car speed summary. So basically, you can see all the percentile it's a 50 or 75 to give you all the status the status are here. So this is the kind of that.

A

Also, this catalog is kind of Peres static um and also you can feed into your promises like the dashboard and then you can query any particular metrics and as I mentioned earlier, so it's uh you uh like all the Matrix is still um under like a host like Matrix. So it's a you can see here. All of them are still under like this microphone Matrix and these metrics that contain the base, uh also the vendor and application and a customer scope.

A

uh Amanda application, as you can see here like this, is the like- has a particular Matrix I can see if I directly putting here, uh you can see the rest requested scope, so you can see all the Matrix without automatically like a listed. So here you can see the micro profile Matrix, or some of them are yeah they're they're the base and also in the URL here, um if I want to say basically I want to see like the base foreign.

A

Like a yeah provided is Awards in in the basically required by microbiometrics each implementation monster provides. So this is a vendor Matrix. Basically, vendor has some Choice which one they want to provide. So this is a customer scope, so car scope, so you can see like um this is like. If you specify the cost scope, you just get your your this customer scope Matrix. So now, if someone like specify my Matrix, so Emily, Matrix I can just say ml scope, I can use an Eminence group.

A

So I know like this is the metrics I created I can make a like a filter is through an Etc. So this is a kind of quick um like run through about like macro profile, Matrix 5.0. By the way, if you have any questions, please feel free to post on your questions on the like a chat.

A

So let's meet Karen with the next one, which is the microphobia Telemetry 1.0 again I mentioned earlier, um like a micro profile, open, chasing I was moved out and the micropod Telemetry when the O was moved again. Why, um probably Now by now, you know, is that the open, tracing and open sensors merged together become open Telemetry, as under cncf I. Also I briefly mentioned, like open Telemetry has three pillars: tracing a matrix analoging.

A

Why we like the like. uh We look at the micro profile Telemetry like a like a replace tracing. First, that's because the micro profile Telemetry, like has a main color treason. Api is stable first, so it's they focus more time out together chasing out, and then they walk us through like metrics and also the login. So um with that, so it's! um This is the words in the micro profile, Telemetry 1.0, by the way this is um television 1000 is all has been released to Maven Central.

A

So also, if you can find out the stack and Etc it's a very small specification, so the amazing is that it adopt open Telemetry. Changing it does not. Disrespect does not provide any apis. It's because open Telemetry is already stacked. We don't really want to wrap it up and give you a new apis. So it's because I think that's going to be a mainstream.

A

um People will more familiar with open Telemetry. So what we are trying to do with micro profile Telemetry, we want to make the decline.

A

Application developer to easily adopt telling me open Telemetry, so one thing the open, Telemetry tracing is disabled by default, so you need to set up the property Hotel, the istk dot disabled equals. Fourth, why it's? Because it's a kind of we want! You conscious! You want us like a turn, a tree signal, so this is so easy that you just configure it and the things that you are conscious. Yeah I want to choose. It's no longer a thing, no matter what you want or not, you have the chasing.

A

You have to use the cheesy, so this is the kind of the like the we want you to understand, so you you can like enable it and by default, because you, unless you said so, we're not going to push you to the face- and it has three types of instrumentation automatically in instrumentation manually, like instrumentation agent, to support so for the automatic instrumentation. Is that if you have like a restful web services and also micro virus client or they are automatically twist, so it's all these method automatically Chase.

A

So you have a taxes like a get operation put operation Etc the automatic sheets for the menu instrumentation. For some other additional method. You want to choose and you can like a trace adding manually to it. So you could either use some like annotations, like with a span or you inject the trees or stand and Etc, or do programmatic, lookup spinal current, or something like that. uh The the agent instrumentation you can use the open, Telemetry Java agent to directly like to gather Telemetry data without any code code modification.

A

So basically, when you, so they are application. We just added the job agent parameters. You get all all of the trees, so I want to emphasize microphone. Telemetry adopt open Telemetry apis, however, is simplified. So basically it's the integration with the Jakarta ee, like a Technologies, is a provide CDI integration. So this is the main main like standing point.

A

So this is a quick overview. How it works, so you can see is basically, if you're, using the put in the open shift environment, you have the restful web services and then the kind of recording like a each other. However, all these trees will go to open, Telemetry, collector and also by optionally. They can go to the Gateway, open television, collector and then okay, you can like uh director to Diego or the king or some other backend.

A

So the micro profile telemetries, is, as you can see, you can use The annotation like with the spans by attribute, and you can inject open Telemetry on the trees uh on the span and baggage and Etc, and then for the exporter. You can like support your like a favorites exporter in Liberty with positive King, yoga and others. Basically, all so, you can bring you your own exporters to other other exam like a dependency in your home and doesn't like a plug into it.

A

uh With that, let me do another demo for them, like the tracing.

A

So you might, uh this is like the uh prison aspect. So I have two uh like the microservices one is the uh application, the other points documentary uh yeah. Why is the system more wine inventory again the surprise surprise? They are still rest for web services, and the unit system is very simple.

A

You can see here the application and also since my Resource, as you can see, this is just like very simple get operation, so it will like displays the system, the get properties, so that's an important as you can see here, system and slash properties. uh So let me quickly go to the uh here. So basically, is that in order to save time is again is automatically running. So here is the terminal. As you can see, this is on my system. Dot property is, and also I, have a yoga and like um uh yoga client running.

A

So if I do a fan of trees, I only have one spam, because it's on his own I did not call anything else. So it's the as you can see here. It is bad. So this is like a one application. It did not go anywhere, it's not very uh like exciting. So next one like uh is a Elementary, so it's um inventory again is like the uh Texas application, so you have application uh other than you have some resources.

A

You can see here the get operation like uh tendency systems and also host the name and then we'll get a property for host. It has a pass Prime um and it is we'll call the get. So this is the manager.get so that the manager is the inventory manager to inject into it. So this is the the CDI bin application scope, inventory manager. It has like a few. um It has a few methods. One thing I want to mention here is the kind of basically uh is not just as resources.

A

So what I want to do is I just inject the Tracer, so here's the Teresa Tracer is like the uh as you can see here like open, Telemetry, API Tracer. So it's uh and then it's a get operation. Basically, you can see like the basically when you, when you do, uh when you do a kind of integrator you can see. Trees are those band Builders, so basically create a span and then is basically look at the properties span and then you can add event and then you end it and then the other operation.

A

These are get operation, but this is to get some methods. The hours ones are like the property, uh as you can see here the trees and build another and add a property. Another thing is kind of the set of property, and later you can see this other events other things kind of the is the end. So uh so this is the inventory manager. So it's basically in here is inject the inventory manager into the drugs as resources. Since you get a manager and first you do the manager.get.

A

So that gets a method that get my method. Obviously we'll call that kind of the creature. Once then yeah another thing is another and then we'll call it add, will again we will create another span.

A

This is the so this is the. This is how the like Elementary works and things they cannot. um Let's, let's go to the Poke that URL, so basically so for that.

A

For that, so basically this is the kind of the elementary systems and the localhost. So basically I call this localhost. uh It's uh if you re, um if you can recollect it, it will go to the to the get and then later on, we'll do an ad. So now, if you go back to the to here, like the.

A

You build three to the service name in entry, so you can see it's like. Basically, you've got five spans, so this is the first that you want to read. This is the kind of the the endpoint and then uh called the inventory gets properties. The first is Again Properties now again properly. Actually it's a coin to the system like a routine of the property, and then you do a add property. So it's do the add property.

A

So it's uh as you can see the oldest bands, the Accord uh basically connected together and from the one trees. The one thing I have not shown showed you, which is you think? How was the magic could be made? So it's uh like, as you can see here in the system like uh mentioned here in this, um like I use, the nothing I didn't I did not use any like open television actually apis. So this is the kind of automatic um kind of the basically automatically instrumentation.

A

How did I enable it so very simple, so all I need to do. I will say: okay, I, wanna, Trace I, just say: hotel.stk dot, disable equals force, also I specify by the way. My exporter is Yoga, so that's why I plugged a year yoga- and this is my hotel service name system. So this is uh like um how it works.

A

It is automatic and the other one is kind of documentary which I showed you earlier is menu again no surprise here you have to see okay, I, wanna, Trace I know again, my X quarter is a yoga and my service name is elementary and the thing is, as you can see here, I just demonstrated ideas that did the injection for the Visa. So in this example, you can see here like the menu and then go into the like the automatic and back to um menu.

A

As you can see here, the system client is a basically because it is, it does cause get properties. So this is the system, client, together properties and that's good to go to here.

A

You go to here, so that's the like why, uh in this um like attrition, you can see the system properties that actually went out to another service according to the system, client according to that and the URL, and they try and come back again. So that's a quick demo of the micro profile uh tracing micro profile dynamic uh with that, let's quickly, let's go back to like um picking into the future.

A

uh So if you want to try out the macro provide 6 to like do the first movement and also we want to do more Innovation, we want to add more spare and use facts and also innovate the exit existing specs and also we want to grow awareness and options for macro profile. We want the strings the brand.

A

As you can see, we have new members and also we want to expand the macro, providing different, Geo and hopefully get more like the members and push a macro profile further and get more adoption, and also we want to establish the champion program on a plus. We have been pushing hard to grow the compatible implementations um and then without seeing we want to welcome new members.

A

We also want to adopt I want to get I mean other companies to join micro profile working group and again is we want to grow Our, Community, Committee group and also some contribute currency as well. We want to work closely with Jakarta, so basically, we want to continue to demonstrate the Cuttery and macro providing work beautifully together. Nicely provides really really powerful cloud and Native technology roadmap for all the people who want to do the cloud native applications. So it's um this is the aim, as you can see micro profile.

A

Six, we already like uh Embrace 10 core profile, uh the technical goal for 2023. We want to evaluate, like a cloud storage converters, distributed cash and also service programming model. So we want to see whether we can create a service programming models like in any other Cloud. You can directly deploy your macro profile application to work. The work is without any glitch and we want to evaluate you evolve, Telemetry to embrace metrics and open Telemetry logging as well, um and that also I want to try to emphasize micro profile, analytically.

A

We want to align on the ongoing purpose and also we want to have a look at the gap between the spring technology and macro profile to see whether there are any Gap we want to cover.

A

um uh Finally, we want to like improve alignment with the cloud infrastructure, and also we want to follow closely with the Java like the Technologies and social. We want to evaluate like a record on the virtual thread and Etc and, as you can see, we want to explore versus real usage in micro profile apis and also we want, because Cloud technique, knowledge moving really fast. We want to like stay close closed, captioning not available.

A

To Amazon to like to have look at this book and this book I could authored with a few of my colleagues so with that. Thank you so much for watching tuning in are there any questions?

A

No more questions yet Emily? Okay, that's great! Okay! Catch up with me, like my teacher, almost done, and if you um questions just uh yeah feel free to get in touch with that. Thank you so much again, thanks so much Emily. That was great. Thank you.