Jakarta EE Tech Talks, 27 Apr 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Cloud Native Microservice Programming Model | Jakarta Tech Talks - March 2020

Description

Creating cloud native microservices is common, but which programming model should you choose? At the moment, MicroProfile and Spring are two popular programming models for developing microservices. What are the differences or commonalities between them? This session focuses on comparing the two programming models side by side. After the session, if you are a Spring developer, you should be able to grasp MicroProfile very quickly, and vice versa. Since MicroProfile is relatively new to the market, this session also includes a quick demo of developing a MicroProfile microservice and then deploying them onto Open Liberty.

///GET SOCIAL!

Subscribe: https://www.youtube.com/user/EclipseFdn
Follow us on Twitter: https://twitter.com/JakartaEE
Like us on Facebook: https://www.facebook.com/JakartaEE/
Join us on LinkedIn: https://www.linkedin.com/groups/13597
Tag us: #JakartaEE
Want more great Eclipse Community webinars? Become a member of our Jakarta Tech Talks Meetup: https://www.meetup.com/jakartatechtalks

A

Thank you everybody good afternoon, good morning, I'm good evening to you all so in today's talk, I'm going to talk about two popular programming models.

A

Microfinance bring actually focus on more on this brain boot aspect since I am a medium I'm, a Java champion, senior technical staff, member IBM I'm, the Liberty micro service architect, so I work, minim, open source projects like a micro profile on open a party in today's talk, actually ISM I want to give you a kind of different perspective, so I'm not devalue any programming model. Basically, I want to put in a context for someone who knows the Java EE.

A

From this talk you will know a little bit about bringing put and for the people who know the springboard already. Hopefully, in this talk I, you understand micro profile, which is a directly built on top of Java EE. Next, a place.

A

Next again, please so micro profile has been around for a few years like it's. The it was established in 2016, IBM, Red, Hat, pyaara and Tommy year and known as Java community is being hosted by eclipse so he's under Eclipse Foundation. So that's Hawaii, the code, Eclipse micro profile and then later on, Oracle and Microsoft, and together a few jisu and others or joined and micro profile is a completely community driven is Kunal, is there's no kind of major stakeholder on etcetera? Is a community decided what needed to be in a programming model?

A

There is no reference implementation either. So there's a the oh there's like a thousand implementations. They are all equal because we don't want differentiation which wines better, which ones not so that's why we remove the remove with as a concept or reference implementation. So the API and TC case freely, downloadable from Neiman's intro and a spec are released in the individual macro profile specification release page and we have very light weights in 30 in iterative processes to control some release. So basically, every year we have like a three releases.

A

A

So in the macro profile community, as I mentioned earlier, there's a dozen vendors and Java user group is a today is about 169 individual contributors and is a faster growing about that and independent implementations as well. Next, please.

A

System in a like a tad and implementation, there's a open, Liberty, WebSphere Liberty from IBM and Wonka's world flying sound hello from Red Hat pyaara from P era and Patti Tommy from Tommy Troy and halidom from Oracle, and a patch launcher from fro do so, and cumin was a year from community and also hummock is the kind of is a from community and prana is the new random being released last year? So is that the wiki page I come Oh wicked Oh, Eclipse, torgus trash micro, preposterous implementations?

A

Tell you everything about the implementation state, arson, etcetera next, a place.

A

So your macro profile, as I mentioned earlier, like every year, we have three releases so far like in February 2020. We have a macro profiles, read or 3-pin released, so any moment run times trying to like implement a group of us read or three. So what is the space for the upcoming supporting runtime for these 3ds next replace.

A

So this is give you a quick summary about micro profile. As you can see, the green green box is directly taken from Java EE CDI jax-rs, Jason, P&G SNP. All the blue ones being released is directly involved in the micro profile community, open, releasing hell's magics, open API for tolerance, GWT configure Reza cron, so they are on the Left. They are all in our umbrella release. On the red hand, side they are individual specifications because they are not in the umbrellas back, because we need to get more feedback before we merged into umbrellas back.

A

So they are reactive, messaging, reactive stream operators. If we are trying to do reactive check these specifications out and also the contacts propagation for the concurrent concurrency programming model. Basically, witches contacts need to be available on the newly created the thread: a synchronized.

A

If you do a synchronized way and for example, in photons, if you add a synchronized a it will we will spawn of a new thread for this new thread? Is it's a kind of auto control? You don't have any contacts associated to it. If you want to push the Syriac tax, for example, you will need, is a contacts propagation to associate a particular context with the newly created just right and then in the Box in gray. This is upcoming specifications. So hopefully it will be.

A

Release is really stressed this year, so I would think in the took you at a minimum. We should have a decent specification being released next, replace.

A

So this is a caveat quicker like overview about spring and a micro profile. Basically, they are very comparable and, for example, at a study that you have different as data and also when you create a macro service, the most popular technology knowledge will be arrest. So it's a micro profile. We have just jax-rs in spring, you have a spring MVC and also dependency injection, an API documentation. Restaurant GmbH is MP and also both the programming model over reactive support and also for the operation team, and so for you improve the quality service.

A

We have a configuration also for torrents security and from operation concern. You have a health on MAGIX and distributed tracing. I will go through them one by one and next, like 30. 30 minutes also go to next place.

A

So this is starter. If you have not looked at the micro profile, data go to the statute or micro privada. Oh, so you can view in the artefact ID and also you choose micro profile version and then is microfiber end times.

A

You can choose your favorite around time and then summer and home also supported a tour job at 11:00 and their honor already bought homicide that you have example, specifications so to get us started as recommender you choose to select all so you can I mean you can generate a demo app to demonstrate a you t-midi video specification on the red hand, side that has a start of us bringing IO. We create your first spring up. You use this one and erect a creature. Here's a memory project or great project. You micro profile, starter.

A

We have maven support. We haven't put a greater support as yet next please so you need to talk I'm going to focus on the cloud or native point of view. So to get a started like we will say: I come. How can you create your first or micro service? The as I mentioned earlier micro service is kind of a small application it will have exposed at any point. How can you I can expose at any point is a very good chance if we use restful api. So it's the next place.

A

Next again, thank you, so yeah micro profile, I'm, sorry that the color is not very nicely like a real pupil. So is the in the micro profile. You will use them jax-rs.

A

You will have a two classes, wise application. So basically you have our application path, the other one. You will create restful resources. You will have our path as an annotation and also you specify the format of is a response. So you you need. Example, on the left hand side you say: okay, it's a format on the wire will be application Jason and then you can declare any get operation, and in this way it will expose any point for you to get operation or put operation and set in a spring again.

A

Your is very similar to Metro profile. You have two classes. Why is the spring bootie application on the top? The other one is restr controller, so you have at rest the controller and also you again also need to specify the URL. So here register map him values, / atoms and then it says, is a get whole operation, so he in just as you said, advocate and the in spring, you said: request method daughter get, so this is very comparable.

A

So, like a basically this URL and very the way to do this, you are very similar to micro projects as well next place.

A

So you know like a with like a RESTful API, actually alone, you will be able to create a macro service. The next thing is that also you can create a macro service and you need to make sure internally right internally, your micro stuff is very Teddy. So how high like a do the essential housekeeping, so you use a dependency injection next, replace so in micro profile will use a CDI, so in CDI is a major thing is re-inject.

A

Basically, once you use the CDI and you will not directly go into constructor anymore, you will need to use the CDI this accountant er, to manage all the instances for you basically is there. Hi I need an instance for the inventory ref fresh tasks, acedia a continual contact, a create an instance handle over to you even is an inventory refresh. The task is application. Scoped is every time when you use re-inject, you will get. The same instance is no other instance, just a one single instance.

A

If it's the inventory refresh task is that a hi I am request scope, so each individual request. You will get a new brand new instance.

A

Similarly, in spring I, actually Springs portables is a street rotates, basically is as an injection as an injection and also like, so, which means a sprin supporter at inject spring support adding injector, also spring support at Auto wires. So, however, an auto Wyatt is a kind of user or more than at inject, so most spring developer of familiar with are too awkward whenever you see other Ottawa wired, and if you want to think about a macro profile contacts, you will translate it to be at inject next to the place.

A

So next thing is: how can we like I, create a my micro surveys and then is the kind of I upload I deploy to the cloud Hawkeye document to my API? How do I tell people what I am capable of so this is a kind of documented API. Next replace.

A

A macro profile we use a macro profile, open API, so basically is this- is a macro profile of open API actually is directly influenced by swagger API. If you know swagger API, you can see from this window here from the right hand, side. The open, API response is very authentic, actually identical to swagger swagger API system, so your micro profile, open, API, always did is publish a few annotations like on the top hand, side is API response, basically give you some documentation.

A

You can provide a response code under then provide a description and a content, and also in the also you can provide. What is this operation? Does you can do the summary and also description and in micro profile and with macro, prefer open, API automatic at any point localhost and import and a slash, open, API? You laboured here also, we integrated with the swagger UI as well.

A

If you directly use a starter macro profile starter and you will get a additional enter point- is a slash, open, API, slash UI, so you will get swagga UI like so you can directly invoke any point and see them. I can see the documentation on the website. So looks a is a quite neat next place.

A

Next next, so documented API in spring, basically ISM spring, also use have a kind of category integration with the swagger. So you can directly like you include this snippet. That dependency in your maven project is spring dog, open, API, cool, and with this you will get an important is slash version 3, /, API Docs, which is the equivalent to macro profiles, open /, open API. The other thing in the spring also has the integration with the swagger you are. If you put, it, is dependency snippet, you know maven project pom.xml.

A

You also can go to the URL swagger that you either HTML. You can see the UI version and in spring it has also has some annotations control, advice and responses state hers. So you can, you can add, as a responses status like HP Staters, no found an accession, etc. So it's a so basically it's the macro. Proper openmpi is give you a little bit more invitations and a spring also give you some annotations as well, for you to tease describe, which is each an appoint next place.

A

So after now, you can create standard or micro service, remember, to use a jax-rs and to use CDI and also to be able to document his own. So next thing is micro service. In no stand alone they will need to use invoker some other macro service, so we use so we Jamie in some micro service, a I need to go into micro service, be so easy. The we call it arrest or client next place.

A

So your macro profile res decline. This is all this. Is them not very visible apologize? This is the Kano's. No quality is a quite bad. Let me just talk talk of them through so in rest of the current, your micro profile. Basically, your creature on the top hand side, you create a creator.

A

Interface, so public interface is, is Greg gradually getting better now and here's time to pin to the frame. So this is you target to arrest, register reticle and basically, in my example, a Corning P, so yeah micro-service a you directly like create an interface. Basically is the micro service be like implement, so he is like a and then you do a register, rest client and then yo micro service in your micro service. A in your Jack's resource is interacting inject inject.

A

This instance into your integrate this instance into your taxes resource, you can say, add in Jack at resident client and also is the inventory service, client and the wizard is the macro profile. Rest client, implementation with directly creating instance and injecting into this. This info client is variable similarity in spring. You use a thin client. So, basically is you can say you again is a new macro service, a you Chris, a you creation interface like a micro service being implement it.

A

However, your annotated with a thin client and then in your spring controller, you say in enable thin client you can inject. It is a thin client. I got its imagery service client next place, so this is a kind of come to you can. With this Reza client, you can connect multiple micro services and when these micro services they communicate, they need like a past like messages between each other. So you one cannot format. This message you to convened, so it's um I think it now is a very popular format, adjacent so Jason format.

A

That's why we like Pauline that Jason beyond JSONP micro profile next place.

A

So in micro profile like how we can directly use adjacent PNG S&P from a Java EE, you can use, it is API because it is automatically provided by macro profile in spring, actually is bringing also supported. Jsonp also isn't I think his Jackson was the kind of more popular as Angie's and B. However spring does.

A

The support is in B, says on the bottom side, you can use a Jackson or you can use in Jason B next place, so the next page in this page I give you a kind of a bigger picture about how how do you use the Jason B Angie's in P, a macro profile? So basically is again. I mentioned earlier. The macro profile you create Jax's resource and then is either get or put operation, and then you can say other produces media media type thought application Jason and you have a recent type in this.

A

A written type on the right hand. Side is a human tree list. Using inventory list is just like a data model, so is it completely? Is Frank Paju? So in this photo you you don't need to put any special effort in this podium and you can directly create a some variables and etc. It's no different from other podium and the beauty is the reason B rtcp. The implementation automatically see realizes this object when the put on a wire and when the retrieval of the wire is automatically deserializing.

A

So this is you don't need to worry about anything else. Next, please!

A

So that's the kind of after now is the imperative programming model. Basically, micro, imperative programming model is the kind of it pointed to point. You know which one you are calling according to, and you know, is a kind of service. A go into service be in service, is, is not a broadcast in any mess, it is services. A knows its consumer, however, is the one will happen like you want a stream messages, and also you want like broadcasting messages. You don't even know like where your consumers are, how many, how many there are.

A

So you know at the moment and a lot of people started using Kaakha Kaakha Kaakha, which is message broker. Basically ism. You can directly push a message to cop car and then consume message from Kafka. So similarly, how can you like use this one together with a micro profile with Java EE, so a macro profile we create as a reactive programming model and similarly spring and has a spring reactor and etc is a spring like a reacting reactive programming? So it's a macro profile.

A

We created a true and Easter to were used as annotations, while are also going the other one at incoming. So our auto going is a tunnel publisher, so you publishing message to a message: broker I. Think incoming. Is you like a creature, a consumer to directly consumed from a channel?

A

So in this example here I got other going, I push message to a channel called channel and they are the incoming at already consumed message from this channel. So, however, where is a channel lives? Lhasa directly can configure the you know micro service application.

A

It could be you like user Kafka or could be you use active mq or mqtt for etc. So this is a micro profile, reactive also, you can use some axe job. This reactive programming, like api's in spring, and also it has a quite a good sport with with the Kafka so in spring and on the top one on the top could a snippet. You have a cop car listener.

A

Basically, this is the kind of Kafka consumer, so you can consume from which topic topic is users, and the consumer group is a group ID and the other thing is on the bottom hand. Side is spring, is economist? Bring publisher, basically, is the converse any more messages to cop car, so you can't Iraq the injector Kafka template and then can this is sending message can directly send message to the cop car template cop car template Dawson's into which topic with which message next replace.

A

So it's um now is the kind of whole programming model has been done, so is up to now you you can do imperative or you can do reactive and now it's like that's a basic in need. It has been covered. So next thing is that you want to improve your quality service. Well, hey! If you have a hundreds of micro services, how can you manage them next place so ISM? If you have a hundred micro-services? Actually you want to also use the best practices as well.

A

Hotel factor and the inter factor up put a certain factor is configuration basically is a kind of externalize your configuration. So if a macro service a deployed to the cloud a and and then it can behave nicely and then later on, you deploy to the cloud the B and also is you want control the behavior database. You don't really need have to reopen micro service, a and recode it and then change the configuration and the uploader to cloud B.

A

Obviously, if you externalize your company region, you can directly control the coming of value in the cloud infrastructure. So that's the configuration next place.

A

Your macro profile, we have a macro profile, config a macro profile, configure it has an ocean Metro profile, configure sources. So basically you put all your communication. You know committed sources so basically, on the on the on the left hand, side in here and you can create a classic search and Segoe UI. Oh and the Zen is the kernel index and then doctype or in your configures rules.

A

These are configured so that could be in an environment, a variable or in a system property or inside a your macro profile application or, if you put it in the coronaries you can put in the company map, or you could specify this in them like in the zookeeper or in database anywhere, and the beauty is with the back row, profile conveyed and no matter where your configuration is specified.

A

You can use either the API like a configure provided or the config and then configure dr a value and putting in the property name and also the type, and you can retrieve the value. Alternatively, you can use a CDI, you can use adding inject at a configure property and putting in the property name and micro profile can take implementation automatically inject a URL and the introduce a variable URL.

A

Similarly, in spring spring again, your right eye is reckoner. You can put her some company or property in a comical sauce. In this way you can specify in anywhere spring candle opening in configure sauce. In these ways you can specify galactus search and also- and then you can inject, like a configuration properties with the prefix, elastic search and I can directly inject into all the variable there, and then you can do even inject. The who class like an elastic is served config into the conve, so spring actually have the concept.

A

All these almost grouped I mean configures, configure properties. A macro profile is kind of flat, so we have two do's and trying to support, and similarly as a candle structure, the configured roses as well.

A

Next, please so next one is: how can you create her like a resilient microservice? So how can you make sure your macro service behave all the time and under whatever the situation is so you need in case you want user for tolerance, quality service to control, microservices next place.

A

So your macro profile, we use micro profile for thorns in macro profile for tolerance. It has a few IP annotations, rich white I'm out circuit, breaker, fullback, I synchronize, and also has a book head so rich. Why? Basically, if something doesn't work, you want to reach whoa, that's a pretty kind of normal and time out. If you have kind of time, CLE critical operation, you want a control under what time limit you must retain our response to your to your customer.

A

So this timeout Evie is the kernel. You go into an downstream service and take a longer to respond, and with this timeout a plug-in and no matter what a response you get back, but within this, for example, if you specify a two-second, if you don't get any back and the response within this two second, you will reach an error to your customer. So basically, with this is, is with this error. Actually, you can trigger the fullback so also with this operation.

A

Probably you need to think about what was the continuity plan, so you will use a fullback. So, in this case, like you know the SM problem and the four parameter for that inventory will be code instead, it will provide a cannoli for the response to you to the customer so in spring, and also is the be used history, bringing his tricks and also it has some annotations in this. One is also spring: hystrix has a fullback and has circuit breaker, have a read, Y and also has a book hat and etc.

A

So pretty much like her pretty much like a similar to macro profile. So the only difference is bring. You knows is a wrapped on history's a macro profile different. The implementation has a different way to achieve these four horns aspect and the some of them use I think is the most Ram. We do not use history, some of them yeah created their own implementation without using and instead of honey libraries, so he in spring you can see in the history command.

A

You have a fullback method and also you can have an enable a circuit breaker next, please so the next one is how to secure micro services. So it's security is very important in the micro service architecture. Let's go to the nexus right to see what difference between spring on a macro profile.

A

Next, please so in micro profile is the security aspect it's directly built on top, so Java EE security, so it'll use. The rules allowed in this example. Here is operational. Gwt based value is that actually only the access group product is allowed to use this operation. Other others are not allowed to omocha nice operation, so micro profile, GWT derogative, build on top of GWT, however, is other two claims.

A

One is the UPN, the other one in the access group, the other one in the group basically wins identify who the caller is the other wines that identify which acts as a group. This color is from so with that information when the back and the received is GWT, it can open up to funnel is claimed to be able to tell whether to determine where whether the user is allowed to invoke ELISA and point on or against bring it has and enable web security other than interacting injector GWT config.

A

So you can directly use any API, as in the GWT config, to control your endpoint next, please.

A

So the next one is hopefully I use the next few minutes and to cover the ugly covered. The ops aspect- next, please so the first one is your macro service need to communicate with the backend to see is whether micro service is healthy or is ready to receive any requests. So the first one is micro profile provided as a readiness check. Basically, this is a determining whether is the micro service is ready to receive any requests. The next one other. The the second Hawaii is the the Lebanese chap.

A

So basically, with other lioness Salah means you can directly put any logic in there see with other lioness. You can say: okay, maybe around her memory and etc. This micro service is going to die and this payload with directly exposed under the and opponents ration health start life.

A

Similarly, the previous readiness check it will be directly exposed to stress health stress right, so you spring, it has one and the point exposed is a slashing health. So you can you can directing implementers health indicator and again putting your business put here. Your algorithm there to determine when to make the slash health, responder error, code and etc, and if you want to use a spring with the kubernetes, a property you have to create another and appoint wines, the Connaught / Hills, the other.

A

Maybe you want to slash else's life or / variety to be able to plug into the Coronet his lameness and readiness check. Next, please.

A

So the next one is like: how well can you know whether cano your macro service is behaving? Obviously, you will need a matrix data, so a macro profile. We have a macro profile matrix. So is this macro profile matrix you can directly plug in with vicious or Gravano, is a candle it directly, and then it has a few annotations at times to calculate how much time it used for invoke each like up the corresponding operation or contact.

A

How many times have been invoked and a metered, also kind of coding, frequency and etc in spring it has kind of equivalent. You have a counter service again in the spring actuator can plug in it has a counter service. You can figure out how many times is a an opponent has been cold places, an extra place.

A

So the next one is tracing aspect again is previously I. Hunted me, a your macro service is no standalone. Itamae Cohen, true I mean quite a lot. Other macro service to fulfill up operation says, however, if you do not know how many micro service involved in a particular operation, even our crazy knock in well, you need to figure out which macro service is having our problem. So with this, you need some tracing these location, your micro profile. We have a macro profile, open creasing, so which disease is a kind correlate or the PSID.

A

So basically it's for user operation. You can go through the tree. Sir I got a tree star like yeah, go zips, zipper, keen and to be able to see them as a whole Tresa. So, basically that you can see all the pieces spent to associate with one operation. If something is not working and you can see straight away in spring, it has a spring cloud as ruse and also cannot a gimmick in occasion. Chain will automatically trace. Your micro profile is the old Jack.

A

Where's Jax is in vocational automatically trees and also, you can add, some additional trees. I. Can you use out of twist to any other, particularly non Jackson as method and etc? Next, please.

A

So this is the phenomena that take away. So basically is what I want to say is both macro profiles bring provide developers, the CUDA programming model, 14 micro services, so developer can choose whatever they want.

A

So if they have a java year background, maybe they will find a micro profile, it's easier if they are comfortable with the spring yeah it's they can continue with the spring, because both of them are pretty good technology with cloud native, my application development and also is a lot from a rental application service portables, like opening party like a Liberty with pop-up spring and micro profile and you're free to choose whatever programming more.

A

Do you want spring has been around for probably more than 10 years and quite popular a macro profanity cartridge evolving rapidly, and it's gaining momentum and I mean since last year and bosom like us, bringing a micro profile and provides next-generation cloud native application development for the cloud, so they are quite a similar from what I have demonstrated in the previous right. However, there are some differences as well. Next, please.

A

So this is slightly kind of very like a man, a very like simple way to list all the differences, so macro profile is open source, so, driven by community it has a thousand implementations spring is provided by a pivotal, so convention over configuration, a macro profile is open. Standard is behaving in like accordance with specifications so that different vendors come together and also community come together to like agree on the specifications and etc and also a macro profile.

A

If you use different, runtime and and the other kind of server a configuration, but it's very many more your application api's will continue run without any problem. You don't need to change your code whatsoever and you can get it running on the different runtime and the in spring is there's a lot of API for you to choose from you can do whatever you want and the other. The other thing is a macro profile.

A

Implementation provides a also. A kind of API is for you, the implementation for you. You don't need to package them the memories with your macro service, so he help home. All you need to say is you depend on the macro profile. Api's, yes bring. Probably in spring, you will need to bring your dependencies. You can say: okay, we should dependencies. You want an essential, putting your pom.xml and any micro profile. We promote a thing was basically because all the implementation is in the micro profile, runtime implementation, your application is pretty much small.

A

You only contain your business logic in spring. You can either do a fancy-ass. Basically you a package of all the libraries with you or you use the Jiva for containers to come up with Asmodeus with that, that's all for the comparison can go to next. Please.

A

So the final page is the references. Basically the all. These talk it directly taken from the IBM, a blue computing exercise, Mac research, other micro service from spring to macro profile. The series blogs, so you can check it out. Also I wrote blog on Android Clips newsletter and then check out macro, privado, IO and also spring that to I/o. And if you want to try some lightweight around home, you can go to open a potato IO or you go to, like others, pyaara or Tommy Tommy, ye or Parkers to check it out.

A

If you want to get in touch with me, follow me on Twitter, Emily, f, HL or ask me any questions. That's off for this talk, I apologize for a few minutes over.

A

Here um any questions so.

B

Let me see if we have any questions. I was not looking at the chat at all.

B

Well, of course, everyone is saying thank you or whatever one, but a lot of people or thank you and they're happy with the good compression between the two frameworks.

B

The stream is available right away at the same link as.

B

Sorry, the recording is available at the same link as soon as the session is over. So you can, you can definitely view the recording. It will be also available off of the Meetup and the YouTube channel as well, so it will be available for reviewing.

B

More. Thank you. Any questions for Emily.

B

It seems no questions Emily again, thank you for my site. As always, it's a pleasure to talk to you and listen all the things that you can share with us with regards to micro profile and it not only micro profile but in in this case micro profile.

B

We will be in touch and please stay tuned for the next tech talk as well as I. Think tomorrow we have a Jakarta update call, so please tune in for more more news on micro profile and Jakarta stay in touch, and thank you so much once again. Thank you. Ok, bye for now, bye.