Jakarta EE JakartaOne Livestream 2021, 14 Dec 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: MicroProfile 4.1, 5.0 and beyond | JakartaOne Livestream 2021

Description

MicroProfile 4.1 was released in July and 5.0 is around the corner. This session will bring you up to date with the latest release of MicroPorfile with a live demo and show case the latest release of MicroProfile. Finally, Emily will discuss the future direction of MicroProfile.

____
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

Hello, everybody um thank you for coming. So in this session, I'm going to talk about a micro profile 4.15.0 and beyond I'm. I am legion from ibm, I'm the cloud native architect which, including microprofile and ngcarta yee, I'm also a chief architect advocate for ibm. So it's in this session. So I will briefly talk talk about some micro profile photo one and 5.0 and then beyond so also, I will do a a bit demo about how to use the micro profile 5 and together micro with the micro profile photo one.

A

So just to give you like um a quick um like a road map is a release, the timeline about the in the past. What I would have done in microprofile, actually microprofile has been like five years old, so we have 14 releases, so it's like, like um normally in the past, probably 23 businesses per year, but they see this year. Last year we made it because, with the working group set up and etc, we managed to do two reduces per year, hopefully from next year, we're back to the three releases per year.

A

Since the micro profile photo, one was released in july, like in july 2021.

A

So in microprofile photo one. uh Basically, it's um there's a small three uh updates. The first one, the health is reader, one so in health schedule, one we added a startup annotation and uh which is the kind of uh kind of the um align with the latest of kubernetes um addition of startup probe. So this is directly trying to provide us as a like a link to the startup probe, and with that we also expose the endpoint slash health, slash started the second one in the channel we publicly announced the dependency on the jakarta annotations.

A

So previously is the hidden behind the scene. And now is we put the decatur annotation on the surface. So.

B

A

See our website we put this building block in and the third thing is, we kind um publicly define what it means for the compatible implementation compatible certification. So basically it's a when we release micro photo one like we have to release it together with the compatible implementation.

A

So and also we defined what it means for the compatible implementation, which means you have to as a compatible implementation. You have to pass all of these eight micro profile specifications.

A

um All these ttks uh passing the decatur yi dependencies like cdi json bg, jsonp, jax, rs annotations. They are optional, so it's um uh because it is a like. uh We haven't um like uh pulled the full uh cdi on the address, so it's very difficult for summer runtime to pass the full cdi, tck and etcetera, and also there's some tck like a northern standalone, so it's very difficult to run.

A

So this is another like representation of the macro profile photo one. So, basically you can see. The only um update is the health 301.

A

For the compatible implementation, so I mentioned earlier like um in order to read this photo one we have to have a compatible implementation. um We use open liberty, 2108 dash data to push the micro profile photo when it is out uh and also it's um open. Liberty. 2109 is the first compatible implementation for production use and then very soon, like a podcast and world fly, they all um like uh yeah certified against the micro profile photo.

A

One uh also, I heard there's some other runtime, like also is trying to certify against microprofile photo one and then now the more exciting stuff is the micro profile folder. Oh, so in the timeline I showed a micro profile photo one. Oh no 5.0 is going to be released in december, um actually I'm very proud to announce that it's released today. So basically, it's like um an hour earlier. So it's um one hour ago I pushed the ascendant, come through the ballot and send a message to the working group.

A

Basically, we released micropro for 5.00, and now, if you log on to microprofile.io, you can see the other kind of materials has been updated, reflected the micro profile for 5.0 really really excited. Thank you so much for the bigger community for putting together. We work together and get these videos out.

A

So this is a brand new microprofile.io website is, it is a kind of redder steelhold from oven, so it's uh this is just updated, like uh is that an hour ago, so you can see it's now. If you log on and click all the the buttons you can view all the kind of the links to the radius, artifact and etc.

A

In the micro profile 5.0, basically it's um what is in the microprofile 5.0.

B

I mentioned the.

A

Red I mean earlier like 5.0, basically, is the it's aligned with the jakarta e9.1.

A

So it's um basically, as you know, macro profile build on top of the five decoder specifications, cdi json b, json, page access, annotations and previously, like um we at the beginning, we use the year 7 and then we align with the year eight java, y8 and then last year december will align with the decoding gate and then now, in this year december, we align with cutter 9.01.

A

So basically now is you can use your decoder namespace together with the macro profile apis, so which means all of these. Eight micro profile specifications have a baccalaureate incompatible changes because previously they used javax now is the the imported culture.

B

A

And, as you can see, this is all the building blocks. um On the left hand, side is the blue, because it's um they all got updated and also they got a major version bump and also on the right hand, side. These are standalone releases, um I'm very happy to see the context of propagation 1.3 was released um like uh earlier. So it's uh also is microprofile community trying to like release the new version on the standalone specification to align with dakar 9.01.

A

So one message I want to pass on is: we are very supportive for the jakarta community so trying to keep up to date with the decathlete disease.

A

So we want a demonstration, microprofile, plastic culture, very powerful.

A

So this is the kind of another detailed message about micro profile, 5, uh oh so, first one is very kind of that clear is that we align with the dakar, yi 9.1 and all of these eight micro profile component specifications uh like a configure for tolerance and health and et cetera. They updated the dependency from javax to jakarta and in order to minimize the migration effort.

B

A

So you just concentrate. Basically, this is just like a name space change, so there's no other functional, functional change, change introduced in these specifications. So this is all the only change. Is that a java x to jakarta um like a name space change so for the implementation. So it's obviously in order to release the specific situation.

A

We need the implementation. So at the beginning of this year, you if you were involved in the bigger discussion. So this is a bigger challenge, because there's a kind of uh the implementation need to cope with the java x because of their customers.

B

A

Customers do want diabetics and also these other customers want to use a decathlon, so they there's a big um like a challenge like for implementations. Those are they need to like um cope with the both java x and d culture. So some implementations uh like um uh had the approach they directly perform a source source level update from java x to decatur update, so they release a new version, particularly just before the jakarta decatur name space and the summing implementation just use the eclipse transformer.

A

So in the earlier in the jakarta studio, intellij idea, they have introduced some tool and also is the eclipse transformer, if you not have not heard of it, the brilliant tool to like directly transform either source or binary and from diabetes to jakarta. So you, like you, can use eclipse transformer directly, transform the binary from java x to jakarta. So it's a the like eclipse transformer.

A

So this is a the this first link is the kind of the the github ripple for the transformer, the secondary in case um from on the open publishing on the open liberty blogs by uh tom bitanti. So he spent a lot of time together with bj hargrave, also from ibm to develop these eclipse transformer. So it's a if you not. I have not seen this blog and check it out. It had detailed uh like a usage um for you like, I have an instruction. How can you use this transformer?

A

So basically it's um you know personal ibu. You can use directly download the gr and then you specify the uh the location target, location and output location, and then you you go to your uh like the binary or source file directly transform. I have a little demo uh later, so you can. I can show you so this is the kind of the uh in order to reduce the 5.0. So we we have to come up with a compatible implementation.

A

Again, uh I led the effort to get the 5.0 release down using the open liberty um as a compatible implementation, so open liberty, 22.001.

A

Like that feature is a compatible implementation, so we demonstrated password all of these eight micro profile components back tc case, so the ttk results um in public.

A

Actually in our internal implementation, we use the eclipse transformer so for the implementation itself, because we use a similar pattern or when we do the dakota yi 9.1 uh like a work. So it's very straightforward. So it's not too much like a worker for getting all these um battery transform. So this is a great or we can yeah. We benefit a lot from the eclipse transformer, so you can try it out yourself, since, if you developed a new application, I highly recommend that you use the decliner namespace.

A

You use the decathlon 9.1 and now together with microprofile5, so it's all the cloud and native apis available to you and then you can deploy to the rental and support both such as open liberty, I'm sure there's other rental amazing in the making as well and they they're going to certify against the microphone 5.0.

A

uh The second thing is: if you have a currently you have application, you want to move up to the dakara namespace. You can use the source level transformation. You use. The intelligent idea come up with some tool or you use like this crude command. I came up with while trying to prototype in some of the very simple um application.

A

uh I highly recommend you use the uk's transformer and then it can transform one like a binary and it can transform the source level since um now is they come naturally to the micro photo one and 5.0 um like a demo? So I will demo. um Basically I will demo.

A

I use the micro profile starter to create a um micro service using like um micro profile, folder, oh and then I want I use the eclipse transformer to transformer, but the source code and two and then I can use get it deployed to open liberty, 2201 dash feature and use them micro profile, five level. uh Let's see.

A

So I have my obvious code here and uh just that.

A

This includer here, let me just- I- have some micro profile, vs code extension pack and I created um like um a web services, so I can see decatur one life artifact id. I just created a use, the micro profile, folder, o and then running on open liberty, and I use javascript.

A

You can use the mimo griddle, so this is a kind of a starter. Then you start a new feature. This year we just released the new starter, it can support minimal or griddle.

A

uh I want to use all of them and but not graphql, because graphql is a standalone.

A

We have to release the new version to work with the decoder names, so you can get it generated into this one to the current project. So here this is the kind of the generated project. So I have a two micro service created uh like uh the service, a and the service b and then demonstrate like um uh like the evocation pattern. So it's a service aid coin to service b. So here is.

A

Can I use the register client directly according to service b, so both service a and service b, is using the micro profile like a photo o.

A

So what I can do, I can directly to say actually some uh I would like to use the fiber o, so I can directly change that because I just released 5.0, so it's uh I haven't uh pushed them all is is a will take time for all of the all this one, all these like binary to end up in them, even maybe ripple, so it's directly used as a stationary wrinkle and then I I mentioned earlier. uh I want to get some running on open liberty beta, so I can specify this property configuration.

A

I get his all of them and running on the opening party feature and let me see it.

A

So, as you can see here, it's I got red all over. So basically now is that no longer be able to see the uh java x, so you can see yeah yeah. I can just directly change. I know it is a technology quadra. I continue that, but you see red all over, so I don't really want to go through them all and then change it.

A

So I can do the same thing for the service b, just to change the changes. The version.

A

And also get his running on the open liberty, beater.

A

Also, I added a.

A

Speech to the ripple.

B

A

A

So it's red all over, so the other thing is that, as you know, I'm going to run your open library since the nozzle on ground 5.0.

A

Similarly, here.

A

Doesn't need to round the fiber.

A

Okay, so this is the kind of the now is. My task is, uh I need to fix. I need to fix all the source code and uh to transform to them from java x to 3g patterning, so I use the eclipse transformer to do it. So it's um so. I uh like, I, should show you the command earlier says.

A

I directly already downloaded um the gia here and I downloaded I cannot specify here is the jakarta wine life? So this is my destination, and this is the transformed.

A

So it's a directly transformed.

A

To cultural wildlife.

B

A

Created I mean.

A

As you can see, here is um all transformed so from java x to jakarta- and I don't have any red lines in here since uh me, she is the so all the other tick cutter to java x to jakarta says: let's have a look all these.

A

So this is a palm, is still cracked uh and also the the server is that basically, it's still running against the microprofile 5.0 and now is that let's go to service eight. Let's start even liberty depth, so I started on them in the demo mode.

A

So you can do the same thing for the service fee.

A

Okay, so it's basically the for the demo mode. Basically you can like start you can. You can start on doing development and then updates will get like a reflected straightaway. It's um to see.

A

This is post service, app.

A

So let's go to the here: it's um services on the uh 1980.

A

Let's go to here, google host you can see here. I can see that it says the hello world. Let's make her absolutely sure. Is this up? Let me see them here is the jacks. As a hello world, I will say hello, decatur.

A

One live: live stream 2021, we see, so you can see the updated and go here yeah. Also, the application seems all running uh beautifully and also is the advanced season metrics and let's test it out, metrics page, you can see all the metrics working.

A

I can see them like uh open api uh as a window is kind of. This is if I do the the ui, because I'm liberty, with supporters for the ui, so you can see the ui um and also this is a and directly call into service b, uh and you show you that, like what the service fee is like, so it's the let's see make sure like her service b is also working.

A

So let's directly go into this endpoint uh parameter. Let me just also say to cut her uh when the base b save that.

A

Yeah, so that's a service b. We are calling about.

B

A

And now is: uh let's go back to see that, like a security, so here is the gwt is directed for the secure backhand. Again I can easily go to here.

A

I can say: okay, um I can't even that is a printout.

A

Intact json, I can india json web talk.

A

So this is the microparty wt, so I can see what is my token eyebroken.

A

You can get a raw token receive that let's go back here, you can see yeah, you could guess how this look. It is token, so the other thing is.

A

The other thing is.

A

A

The open uh open tracing so I have a cheese uh like running in the background and I have yoga running in the background. So it's in the here.

A

So this this is the chicano one. Life final trees, so you can see here is the kind of a second a few seconds ago, and all this has been correlated. You can see this directly according to service b, and this is the service, a and directly point to service b spend the four millisecond in service service b. So basically uh everything uh worked really nicely uh here. So it's. um The other thing I want to show is that I mentioned micro profile 4.1, so in micro profile photo one release. We added the startup probe.

A

This is in here because it's um this is the starter on the photo book, so I can either demonstrate to see here service. I can start, I can do a startup startup.

A

And then I just implement those check.

A

So obviously I define a startup for pro a startup health check, so I have an annotation and startup is this? Is the cdi bin? I just make it the one instance super micro service, so here I written I can return the help check response dot term name named and then I will say my startup check and then I can do a with data.

A

You can see startup started, let's see.

A

True, let's say up: let's build so obviously uh you can. You can just uh put some other chair, because this is just for demos purpose. If you tackle or when your application started. Maybe you just kind of you directly invoke something, and then you get a meaningful response. You know it started, and then you can do that. Let me save this one and let's go back to the uh here. So it has um another point, as I mentioned uh 1980 and then helps uh I then started so this is the new endpoint.

A

So you can see here. The name is my startup tab. The status up here is my data. It started yes true, so that's the kind of demonstrated like the micro profile photo one and also uh five dot. Oh, so is that I use the eclipse transformer to directly transform everything.

A

So that's um that's a quicker demo. For that. Please start: let's go back to talk about what's next, so what's coming next, so it's um basically it's um this year, as I mentioned. Actually, we spent also. We spent a lot of time to talk about to kind of think about a strategy and to want to build a foundation.

A

Basically, we do not want to directly like us keep on evolving on java ads. We know that's kind of the dead, so we just re-based on magic culture namespace also is from the service. It seems is kind of uh straightforward, however, is not that straightforward. We had many many choices. Actually, as a matter of fact, I created like as a google doc and share and then trying to capture all kind of options we could take.

A

We spend a lot of time and seriously debates about how we want how and we can align with the chicago in 9.01 so eventually like how actually we all can see the difficulties and etc and from the implementations etc. So, eventually I volunteered to do the prototype and the demonstration actually it can be achieved so as a community yeah. This is great achievement and this is really really good and set a very stable foundation for us to focus on on the innovation next year.

A

So the next year will be focused on our technical goals. So basically we want to do the tasks under all the technical goals we laid before in front of us. So it's a way really seriously about jakarta, namespace we're really seriously about the chicago yee. So we want to work really really closely on like a cooperatively with the jakarta y uh like other. This is um uh like a community.

A

We want a doctor to come here, namespace across asset, so these include all the demos and the kind of blogs we wrote and previously only work with java x. We want to spend the extra effort trying to like migrate them to the department name space. Also I mentioned earlier, so we want to align like the standalone specifications to descartes 9.1.

A

So it's the as an demonstrator mentioned earlier context. Propagation is the first standalone stack already uh they can achieve that goal and the next one is the reactive for stream. Operators react messaging, li and graphql.

A

I know this is all the the the people that uh the group I'm trying to working together and trying to release the leica jakarta e 9.1 alignment. um So it's the new thing. uh What we are doing is the tracing. So basically it's.

B

A

For the tracing, as you all know, the open tree seam is basically is an in-maintenance mode, because the open tracing and open sensors merge into open telemetry. Obviously, as you know, macro for open tracing is based on open tracing. Now we need to rebase on the open telemetry and then, even though the open telemetry is directly merged of open tracing on open sensor, however, they are still different. So at the moment um the open, telemetry microprofile, open telemetry group are working very actively trying to like uh adopt open telemetry.

A

If you want to get involved, please just like get in touch with me or just send a message to the microprofile google group. So this is the uh tracing. The other thing, the metrics, um I think, is if you have been to the dimitri's talk um earlier uh like uh about halidon. So it's uh he mentioned a bit about micrometer, so your microprofile community, microprofile metrics group are also are working towards the goal and doctor micrometer again. If you want to get involved, please also get in touch or send a message to them.

A

Like a microprofile, google group- and I mentioned a lot about innovation, so your micro profile and this year we want to put more effort on the innovation. We want to evaluate a new specifications if.

B

You have any ideas.

A

Even though you think oh that's like uh is a really really imagined idea, please please just um like a communicate on the google group, so we can all work together and evolve with some new specifications, so the next one is like this is the converter stack. We have been discussed that last year now we have a like a foundation for the new specifications.

A

I we will evaluate um whether to I can start the converter's specification, so the next one is the grpc again. This is the last in the last year's program plan. We didn't get time to focus. That again is the kind of we also evaluate whether we want to do a drpg back.

A

If you like a notice in the beginning of my presentation, I have the building blocks on the left. Is a platform release on the right? Is the kind of standalone release um you? You might ask him. Why is this another one? Really because this stack is the kind of new stacks we want to want to get some feedback and also want to see how they can interact well with the platform specifications and now is that we need to kind of seriously look at this standalone stack so evaluate each one of them like a reactive respect.

A

Maybe this can still stand alone for the graphical and etc. Maybe it's time for the for it to join the platform step and also for the context of propagation, because it's so naturally fit with the um jakarta concurrency. So we think it's a is the canada. We are already on the move to move it to the jakarta concurrency.

A

So this is the other way to demonstrate like uh how closely the two communities are.

A

So the more like the technical goals we want, as if you like, um uh if you have not heard of the jakarta yeti, uh please like uh stay tuned. Please stay in this conference and watch the kevin sutras talk about jakarta, eden.

A

Profile, so it's um uh we are also in the micro profile community. We want to like evaluate whether to adopt the decadal core profile.

A

The next one is like the indicator: ee um there's, a spec called the beam validations, so it's um we also want to see is, like the other, also they usually open on a micro profile, open api uh like there's a good user case, and to make a micro open api to work with beam validation. So this is a really nice phase for this to interact together. So it's again, similarly, the validation could be used by some microphone gwt and the next one is really really uh I'm really really fascinated with this one: the data access.

A

We talked about some, uh these data accesses back, uh probably in the past three years. At that time, I think is people think is not very mature. I think, and now it's a good time to take it seriously about data access specification, so uh we're going to focus on this actually on the 14th december in the micro profile, like a technical call, we are going to like discuss how to like get started with the data access specification and trying to get people together and trying to evaluate the goals and etc.

A

So the next one is about the alignment with the new java technologies.

A

So, as you probably know, the current microprofile apis, the baseline, the java 8 we would like to like, uh even though now a runtime such as openability supports a microprofile with java, 8 11 and 17, uh however, is the kind of the source level of macro. 5.

A

Api is still eight so, which means we couldn't use some new nice features developed beyond eight, so also, we would like to evaluate uh uh upgrade the call uh the source source compilation level to java 11., so we are going to discuss that so next, one is also because we are cognitive technology.

A

We also is um a look beyond the micro, the api level. We look at the containers, orchestrators and cloud to give us new features and etc. We will just evaluate um uh yeah. I need to for more, um like us um innovation.

A

So that's all for today's talk and let me just um do a shameless um promo format. The book I call co-authors this year is called practical cloud native java development with macro profile, so it's available on amazon. Please ask for questions so I'll have three million support questions.

A

Those are the first four people asking a question will be the uh will will be able to get a copy of the user ebook. A one-year three-people book on one parent will be available to all of the audience here. So with that, uh like uh please get involved to the microprofile community, and this is the link for you to take away.

A

So let me stop sharing.

A

Are there any questions.

A

So season yeah, so it's a. If is a no questions you can always get in touch with me on the via twitter, so my twitter handle is emily f h, says I'm like a monitor my teacher handle and etc. Since uh please get in touch and uh yeah, you can ask questions on twitter. If you want.

A

So that's um I will give you one more minute to see whether.

B

A

Have any uh remaining questions and if not, we can close the uh this session.

A

Okay, so thank you all for coming along and for your support here and please enjoy the remaining of the conference. It is um hope to see you in the upcoming conference. Thank you. Bye.

A