Jakarta EE JakartaOne Livestream 2022, 15 Dec 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Ideas For Lean, Maintainable, and Productive Jakarta EE / Microprofile Projects - JakartaOne 2022

Description

How to build, test, structure, and develop a Jakarta EE / MicroProfile project? In this source code focussed session, I will cover the entire application lifecycle and present ideas from real-world projects. I look forward to your questions during the session and will answer them in on-the-go.

-

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

Hello, everybody um yeah welcome to my session so today, ideas for lean, maintainable and productive Jakarta micro profile project, so I thought what I can do differently. Usually I hate all the time and uh the problem is: if you only have 45 minutes, you can only you know manage and in best possible case to do some crowd created of the deleted. I said: okay, I will try to show you or what is my idea about maintainable projects today, I challenge, challenge Evar and said he Eva should ask as many questions as possible.

A

You can ask in chat and if I will interrupt me and ask uh questions directly, so I, like interactions, you know this is Jakarta live and it should be not monologue. It can be. You know highly interactive session, which I really appreciate. Okay, so um yeah I, still like Java, so uh I actually do Java all the time and I really appreciate it. So that is uh my my introduction.

A

um Maybe um more interesting is uh the uh the podcast. There are lots of podcasts with various. You know, Java and uh Jakarta e uh people, and um why I do the podcast, because I never have time and conferences. I know just to to spend some time on socializing and and podcasts a great opportunity.

A

You know, because the other, my guests cannot Escape, they have to sit and I have and I can ask them questions whatever I like so I really appreciate that and um so, and there are some of the podcasts which are related, for instance, Jakarta micro profile. So there was a podcast about runtimes or servers, and there is a podcast from all j2e to serverless and um also you know, Lambda serverless, on micro profile on lambdas. So there are recent podcasts. What I also did I?

A

uh uh It will be published soon, a podcast about omnifish, which is also related to um Java in Jakarta. Okay, uh what's also interesting, I think I got a brilliant idea, so what yeah hex TV is. It is a monthly show. The first Monday of the month I'm answering questions, and if do you know the 100th episode hit I got the idea. What I should do is I can I should go, always 100 episodes back and see which questions were asked eight years ago and what's really stunning is. It is almost identical questions to today.

A

So, regarding microservices and rest, so yesterday was the last show and it's going to be published today in nine, and there are exactly the same questions regarding Jakarta: how to structure applications and what I even did yesterday I pointed to Today's Show, say today: I will answer some of the questions. Okay. So if you have any questions left, you only have to go to my GitHub gist and ask the question and I will answer live, so there is no registration, you did nothing um yeah!

A

Okay, um there is registration required if you like, you can attend my online workshops and now, let's start with the content, so first um I don't even know how to call it. So what I did all the time is? Actually this web and CDI container, and um this is how it uh what I saw I would say 10 10 years ago, web was like GSF and Jack sures and Java application service. What we also had we had is this: yellow boxes are applications, so we had a shared deployment model.

A

Why this because Hardware was expensive, so my clients bought a big Hardware on this Hardware with one application server with lots of applications. So um what happened then is? This is actually the model which I still still see in the wild.

A

So this is like payaras whiteflies, open Liberties, what they are doing to say: okay, nice, there is no more separation, uh there's actually I I optimized it already I had one slide with web and CDI container, and now we have Jack Suarez and CDA container, because I have to say plain servlets or web Frameworks I'm, not using them a lot anymore or don't use them only write cases.

A

Usually we are exposing with Jack sores apis to the outside world and we use CDI to be more not even more flexible, rather than to write less code, because we see the eye of writing less codes than without and this is the Jakarta application service. So there was another movement to docker, I I, remember in the first Jakarta live I use a dock a lot, so we used micro profile, runtime and container runtime by the way in a podcast with Bruno Borges.

A

We discussed one hour long because I always said to know I'm Enterprise, developer, I'm using Jakarta servers and he always referred to runtimes and then I got you know the idea. So what runtime means we have just you know one application and runtime and application is the same and uh application servers is usually it means we have multiple applications in one server. So this is the difference to me and what happens in the recent uh years is something like quercus or helidon or Micronaut.

A

What they are doing is they are optimizing a lot at build time, so there is no more no deployment, so this is actually a huge shift. So for me, no difference, but uh there is a lot of difference. You know from from the deployment perspective, what happens under the hood and by the way you can ask questions at any time. So Eva will stop me and ask questions even I. Actually, they're already are sleeping.

B

I I almost fell asleep there for a moment. Okay,.

A

So then I have to speak, louder right or do something dancing or something actually and.

B

And it is uh uh what is the number one technology feature that you would like to see in the next version.

A

It is already in the next question: I would I would say uh CDI light.

B

A

Already part of Jakarta 10 right, so this is I, think uh extremely important and uh in the next version, I think the micro profile 5 is not Jakarta Oh either um I consider Jakarta and micro profile to being the same. I know this is not correct, but most runtime support both uh as I would say uh in metrics uh scope registry, which is also part of micro profile five. So this would be actually one of my things. The problem with jakante and Java e is is like the problem.

A

You know with smartphones, I, don't expect you know. Iphone, 15, 16, 17 or 20 be completely different to the current one, because it is already nice and perfect all right. We get no larger cameras and whatever, but uh there will be no Revolution, and this is exactly the same with CDI we can inject. You know whatever we like, whatever, whatever we like, so what we can innovate right so perfect. Another question Eva and.

B

Not at the moment, but uh please do uh ask them in the chat so so.

A

Yeah, you are 620 people in the chat, so at least no one has to ask questions. Okay, now, serverless mode is actually exactly the same, but we are using AWS, Lambda or Azure functions.

B

No difference there and yeah just wanted.

A

To mention it's also a thing and I actually listened to a session uh um about uh uh opengen, I, think and open Liberty prior to my session and I also mentioned this. So um um what's the deal I would say, the main difference is uh the serverless. Runtime are even more like Java e servers were before because you own the shipping.

A

You know you are not even shipping jdk, you want to say, I would like to have Java 11 or Java 17 and in the Cloudy runtimes the jdk gets installed, so it's actually less even less responsibility for developer and more responsibility to the cloud owner. This is always the idea of application service, okay um design. So but this was you know, I usually talk a lot about several hours, not.

B

A

About about more about code and by the way um how I got the idea of um what I appreciate about uh Java e, um you will like it Eva. So um the story is uh it's a crazy story? Actually, so um I delivered a session, uh it was 10 years ago, um yeah 2012 10 years ago. As you can see, that's me and the only thing was we didn't had any problems with energy back then so I still had no glowing Apple.

A

No more now my logo doesn't glow anymore because we have to save energy, but back then um I wasn't I submitted a talk. Java E6 is the future is now but is not evenly distributed yet, and the talk was recorded, So with netbeans and glassfish back, then it was jdd. 2012.

A

and uh I got reinvited again and I was in Krakow now in two in October. So actually uh I don't know uh two weeks two months ago, roughly and uh what what I did is I I found the old code and I said: okay, we will discuss what's different to now. So what? If we pick? You know the old code which I, which I know preached back. Then this is the future and was it the future? Did it survive 10 years and the surprising thing is um actually I got so many questions.

A

The conference I couldn't actually call a lot, but I did it afterwards, which is good for you, because I recorded the migration. So what I did is I picked the old Java e code and migrated it as an AWS, serverless Lambda and you can see and it took I- don't know 10 minutes. So uh what I really would like to keep in Java is the stability so what's cool about Java? Is that the you know all the apis?

A

They remain stable and um you know I did Java all the time and in all other projects you know they. They picked the framework of the day and they migrated a lot. So um I would say I'm less interested in migration and More in solving problems, and this is what actually the jakarti has to keep doing. So if we change you know CDI, it has to be Backward Compatible, even if it works better behind the scenes, and there is no reason to know to break. You know everything on just because we we can okay.

A

This was a nice story, I think, uh because this is unique. um It was like an accident that I found the talk was recorded, I had the source code and it was like a nice document 10 years after um was it the future or not that it was so actually, if you would Implement a Java 6 applications, you can run it on Jakarta E10 with manual changes, and the code was still more than enough to date. If you like watch the session, this is fairly popular. It was actually a uh interesting story.

A

Okay, um so how to start a project and what I did I watched my recent projects and what you did do my domain first. So what I will do is just you know, hack uh hack, uh pojos. First, it they can have public attributes doesn't matter. So the first idea is not to write very simple code. Why this? Why? It doesn't matter because it will change anyway afterwards, right so write, simple code, then the next one forget about reactive programming. We get project Loom, so you will see in a in our subsequent slides.

A

So for you know, you don't have to to write crazy code just to be scalable. If you, uh if you like, you, know, write nice code, which is reactive, I, think what you can do is you can have you know uh you can write code for reactive resources like Kafka, Pulsa or something or similar, but there is no need. You know to write a reactive code to have an HTTP call right, it's just crazy, so what I also did a lot, but I was uh always.

A

You know like a little bit an alien or a stranger at conferences, because I always said uh what I really appreciating Jakarta are the you know single dependency, the API, no third-party dependency, and this actually has saved us uh recent years several times my projects, because we we had no security issues. The cool story is if there was no lock for J. No, it's not the libraries uh then, and this is actually the service idea right. Then you can.

A

uh You can just focus on writing business logic and you don't have to care whether your dependencies have problems or not, because because, um uh usually, if we used to know back then glass fish, then we bought support from some Microsystems or even earlier from ba web logic, and they they were responsible. You know to uh to patch the uh or payara to patch the servers and by the way, serverless can also mean payarl, because there is a spiral cloud in the cloud.

A

So you just you know, push the war and, uh and you don't have to care about the server so was actually a serverless pyara server right, so um no nice to have design patterns. So um what I also see a lot in projects? You know developers are starting with uh factories and whatever they can, they would like, or even you know, if you start with CDI, there is no need to start with qualifiers. Just use, add inject and just write a simple Plus Code as possible.

A

Whatever you can remove, you should remove and the nice story is you, then you don't have to be expert. You know to write decent applications and every developers welcome regardless, whether she or he is you, know, expert or not. Everyone will understand, take the code, and this is what I appreciate actually in Java the most the Java programming language is um that the Java programming language is predictable. I think it's really hard to write code, which is magic, I mean if you just if you have to use reflection, a lot you know to achieve that.

A

But I mean Java is like language without surprises, I would say um so. I use the.

B

A

So what it means to me is first Define the platform right so if I'm building command command line, clients or the platform with Java SE, just that, if I'm writing, you know, Java server, I have the platform becomes Java, SE and uh jakartae, and micro profile and I ignore everything else, and if I go to the cloud, my platform is the cloud uh and um and and this has to be clearly defined um so also I- don't know how to call it know.

A

Your enemy right um and I wanted to to create a slide, but it is really hard to to how to explain.

A

Even how long are you hacking Java already you started with Java one I think right or one zero one. One is sleeping.

A

You know the if our.

B

I'm, never sleeping you know, I I couldn't sleep for yourself, but do you want a question or do you want to wait to the to the.

A

End I wanted to ask you a question how long you are hacking Java already when you started with Java.

B

I started writing my first hello world in I. Think it was back in in the 97. okay.

A

This was one one. um So what I wanted to say, whether you remember at the beginning of java, there was a huge everyone was afraid to know of being depending on relational databases, because everyone believed we get object-oriented XML database or whatever and uh What uh did the enemy War Defenders right. So we always wanted to be decoupled from the concrete implementation. This was the major of year of the early Java design.

A

You know don't be depending on the database, always go through jdbc, you know, and not even jdbc, because jdbc can change it at a point of time. So when you eat the Dows data, access object to make jdbc replaceable. So this was You Know The Enemy was the concrete vendor implementation. I, don't know whether it was in your project in my in my was extreme, so we evaluated different databases because we back then 1997 until 2000. Everyone was pretty sure that the relational databases won't survive because we get object window or XML database or whatever.

A

It was also your perception back. Then you remember this.

B

Yes, I remember every project we were participating in, we created our own kind of uh or I'm mapping, so so yeah yeah, basically.

A

Yeah perfect, so um this is also my perception, so I mean to know back. Then uh we decoupled from everything right now, if I, for instance, uh go to the cloud with my micro profiler Jakarta. What is the enemy? The enemy's infrastructure's code, because I spend a lot of time fighting you know the infrastructure if I use terraform I have to write. You know thousands of lines of of terraform code, and um you know the the major effort is not not the cloud.

A

I would say you spend a lot of time with the security infrastructures code, so I would say in the cloud your enemies, the time so I, don't think it is worth to decouple from everything in the cloud. um I would just pick whatever the cloud has write simple code and you will win so this is actually the idea and with jakatai and and microprofile uh you can write that simple code still, so um some of the apis become less uh less uh important. For instance, you know um uh security is in the cloud you can.

A

You know, put a lot of security to API gateways. uh You don't have to implement them internally, but um I would say the majority of Jakarta apis and micro profiles are still great and um because you can write in simple code, so the last one is measure first and optimize. So there's also a common one. I ignore any optimizations in the first iteration of the projects and the first iteration can take in all five months, and but you have still measure whether it's fast enough.

A

But if something is you know fast enough, um I would say any optimization is forbidden. So this is my uh um and because you know you spend time optimizing, and this is just I would say.

A

um A simple code is more important than highly optimized code, which will save you I, don't know five percent. You know this, it really doesn't matter it has to. It doesn't have to be no autism, magnitude, uh slower or faster uh I mean it should be a good balance, but forget about optimizations. First okay, then um Java IC features first write simple code. First, we had prefer JavaScript library, so we have, you know: base64 string is blank string is um uh empty uh logging ships with Java, you don't have to use.

A

You know third-party libraries for it and Java 17 ships with record. So if you have a record, um you don't need to know gen to generate Getters and setups, because we already have our records and uh Java 19 and plus is going to be really great, and this is getting even better. You know, with the um with the switch patterns and uh and deconstruction, which is uh called differently in Java I, see I forgot the name, but in JavaScript it's called deconstruction and uh project. Loom will also change lots of runtimes.

A

We already have uh helidon Nema, which uses virtual threats behind the scenes. So what it means is we can write simple code, you know and scale indefinitely, so we have a million millions of threads in a runtime, okay um architecture tips. So again you should interrupt me and say it's not true so uh and we can have discussion. But if you, if there are no questions in the chat which is a Pity, so we start with architecture, so keep it simple and stupid and you aren't gonna need it. So there are the two most important.

A

You know: principles in software architecture, so question everything can ask: do we really need and need it? Then the next one don't distribute so um I, never understood. You know the idea of microservices and I would say more recently, I saw a lot of talks. You know monolithic and whatever I said okay I mean there was crystal clear that microservices don't solve any problems except you know you have the problems but not like. If you implementing microservices, uh your application will run better. This is just if you have problems you can.

A

Microservices can be a solution to the problem, so don't distribute um so I I try. You know to implement a monolith and um it works really good because it's simple. So there is no distribution. There are no distributed transactions. We don't even need to know long-running actions for microprofile no zaga patents. It's just you know a monolith.

A

Of course, you cannot build a huge system as a monolith, so that is the challenge to split the monolith to to to to do multiple applications, because you have multiple teams, but if you can just go with um models and by the way, um I also built several several Lambda functions so uh with hundreds of classes, and they were crazy fast, so I would say it. Java is really fast. So you don't have you know to to to create something with one class and be afraid of of the performance.

B

Is that what you call a monolithic, lamb of Lambda.

A

Yeah, what I called monolithic Lambda is um my Lambda currently is a Jack to race application with several hundred endpoints and 500 classes. I would call it monolithic, because you know the I have it on the slide. I have another um there's another uh School of thoughts, and they are talking about single purpose lambdas and what they are doing. There's just a Lambda I know.

A

If you would have create, read out the delete, they would ship one four lambdas one for create for read and for update and for delete and I don't get it so because, if with Java, it doesn't make any sense. If you are using python node.js, it has because they they or us, because they usually don't have something like hxrs right so um yeah and by the way, either. If you're interested so go to the Lambda or 2D to the audience, and take a look at node.js and python examples for HTTP lambdas.

A

You will see what they are doing. They are using switch statement. They say you know. If HTTP method gets then do this. If post then do this is exactly what you did either with serverless one zero 1997, because there was nothing so you know got the HTTP request and uh in a switch statement of, if else so my you know my do get method in servlet in my first project. Was that long that we could travel with the compiler because the method was too long. So um so this happens again with Lambda.

A

The nice story is with Jack sares, for instance, um quirkus and micronauts they ship with extensions what they are doing, their their. They are receiving the HTTP event and they are passing into Jax RS. So for me, Lambda or not, it always looks the same so asynchronous invocations for asynchronous use cases. Otherwise everything is synchron, reactive programming for reactive use cases and start with nice monoliths. This is my advice and it works good as actually work, great, so navigation help. So if you start the new I, always pick standards, whatever standard means or in Java.

A

For me, a standard uh I would say 15 years ago was and for building now it's Maven, so um um use boring technology whatever in Java and micro profile are extremely boring. As you can see, uh you know, 10 years ago, my code still runs now without any changes. This is great. Sign um start with the least common denominators. Is that okay, uh what runs everywhere? So uh this is uh interesting.

A

What will run on all clouds and if you think about this, for instance, if you have a Jax rest application, it will run as AWS Lambda as Azure function as Oracle function as a bare metal application as a Docker container and then in kubernetes ECS fargate. So we can actually have the same source code and run it in serverless in server full applications, which makes a lot of sense, make explainable uh choices so, um for instance, um right in my current project, I always challenge, though, do we have you know to use lambdas?

A

Why we don't use no Docker containers or whatever? So, okay, we can do you know kubernetes, but then you are paying for environment at least 500 euros a month and with Lambda we can have as many environments as we like and and and and and then the discussion stops. So um because if.

B

You go to the cloud I'll interrupt yeah, so so we have a question about this that you actually answered right now. So that is why you're using lambdas, if you're using a monolithic application- and that is a cost thing- yeah.

A

uh By the way, uh Eva what also changed there's the the for me. The major difference between on-premise and clouds is on premise: um I only implemented the application and I was not allowed actually to fiddle with the you know, with the service in the cloud. Usually, we are responsible for a lot more for the entire environment and, as you know, clouds ship with hundreds of services, and they are very similar if you go to Asia the recent Services Azure app service and Azure container apps and whatever, if they are all identical.

A

But if you look at the economics you will see in one service you pay all the time and the other service will you will pay per invocation, or so they are doing almost the same, so I would say in clouds the only thing which matters are costs and all decisions are around costs. If this is not, if the costs don't matter, we can stop discussion because I will buy the largest largest ec2 machine, which is available in the cloud. You know ship my jar and I'm done.

A

Then I have a cloud native, um but my, uh but it was going to be expensive too expensive. So I would say all all my all my architectures are around costs in recent three four years. If you are in the clouds, if you don't do this, it is the cloud has become so expensive. Then you either the project will die or you will have to move back to on-premise Data Center. If you still have them some data centers are too small. So.

B

Very good yeah, so so you talked about uh uh compatibility and keeping things uh running on very outdated SE runtimes. uh Do you do you prefer, uh or are you using mostly using newer, a generalized version like 17 and above or.

A

Yeah I'm using Java 17 above not uh just in the Leisure, because there's no LTS above 70., but.

B

All my projects right now are Java.

A

17., okay, always always the highest uh Java SE available. So this is a must, and this enables I started with Docker as a Docker started, I was used to know the recent Java because uh that you don't have there were no more huge Java migration projects right, okay and simplicity and standards. um For me, standards means Simplicity. This is the reason why I still like Java in Jakarta as I started. This was uh I. Always you know introduce myself like what happened. You know 1999.

A

uh There were lots of application servers for our single consultant as us. It was you know any mission impossible to understand more than two runtimes and Java e made it simple. So if you focus on Java e, you are able you know to to understand more than you know three vendors, and this is why uh Java e Jakarta micro profile- and this is what I also think that simplicism means standards because standards a subset of the thing- and this is also you are forced to self-constraining yourself.

A

You know it's like I'm, just using whatever's in the API, and what I know is that that this is actually enough. But um if you don't have the constraints you know in Java, you can use, you know Millions different Frameworks, and no one knows what survives. So. This is the problem to give you a concrete example of corkus in all my Corpus project: I just try to stick with Jakarta e and microprofile and I ignore all other corcos extensions. Why? Because the you know the chances are the lowest than the micro profile.

A

uh Extensions will die. Why? Because they are not. There is a small right behind or or weld, and if you used to know other funky corcos extensions, then this is very likely that these extensions are implemented by a single developer to developers and they lose interest and go. You know, there's another framework of the day. There will, you know, cancel the Corpus extension project and and move on and then I I am sitting on the extension and the next Java is e-release.

A

It will die so the ultimate in internal structure, so I do it for years. This is also one of my philosophy. You know if there is a pattern or pattern standard I, try to use it, and the only pattern I know is boundary control entity. It is older than uml. It was implemented, I think by Ava Jacobson I, always confuse both uh Amigos and by Ava Jacobson. He started with boundary control entity and um all my projects for years have the same structure. So what I can give you of a feedback?

A

I used a project with lots of developers, sorry the structure with lots of developers and after establishing the structure, I never got. You know question where I should put the class, so it is obvious. No one thinks about this twice. It's just very good sign, so very boring way of structuring. You know Java applications.

A

So how this looks like this this by the way are the icons boundary control entity, so boundary is uh juxtrous. Control would be a reusable pole Jaws. So, for instance, concretely in Jakarta we have a let's say: a component would be a package here, a package with a Java package with the name.

A

Let's say: uh jakarte live stream management right and, um and the boundary would be like uh stream management start stream, stop stream or chain Stream So in the boundary there would be Jacks arrest with some Jax res annotations, then, would be a pojo with uh without any annotation except request code or application scoped. And then, if we have, you know uh streaming sockets and payment whatever this would be. Pojos which are injected and entity are Java classes with State.

A

They don't have to be persistent, but they can be persistent, for instance, for instance, on premise: I always try to use jpa, because it's great. Why? Because the database was there in the cloud if I have to you, know to set up the database I'm, no more interested.

B

So there is no database.

A

Because the relational.

B

A

In the cloud are expensive, if you need to backup they are twice as expensive or failover, and you have to set up them with maintenance, Windows, backup windows, and you know, uh leader, follower and all the staff. You will spend a days of doing this and if you use something like object, store or S3, you can store. You know, Java graphs as Json objects, and we do it with Json B, for instance.

A

um So, um actually, yesterday, I wrote a a small example for for upcoming workshop and I use, Json B to deserialize the lambdas parameters as Json when it worked great. So instead of using Jackson whatever it's okay, Json B works. Great is one dependency eclipse the awesome and it worked out of the box.

A

Okay. So this is how it looks. My monolith looks internally, so there are packages and I get to know even yesterday. I do a good question about that and the semantics are the following. So the dependency direction is from boundary control entity, never from E to C to B, always BCE. The cool story is, it is sorted also nicely in in the IDE, so boundary control entity and uh the uh the packages are built um according to to a principle called high Collision minimal coupling means. Whatever is in the package.

A

It belongs together, but the package should not, you know, communicate too much with each other because um they they are communicating, but you know the relation. uh Is the ratio is interesting, so whatever there should be more communication inside than you know, between packages and between packages, boundaries to boundary- you know, is it suspicious. I would say boundary to control is fine boundary to entity. It's okay, but we better boundary control to entity and you can have a package with control entity. It means this is a package without Jax or S.

A

So without external or websockets, without no external interface or API, it can be just controlled entity. You can have a package just with entities. This is less common, but it would mean you know. This is just no I'm just Gathering entities for I always point to the book and there are no questions left. So, okay, if you're not happy, you know with with the names we can write another book or find another book and we'll pick the names, but it's good enough. Okay, build so uh Maven is good starting point.

A

Of course you could use Gretel. What I can tell you? Java e maving works great uh with Maven. It is the standard build the fastest build because um we don't need any plugins. uh Important Maven is not cicd. So what my Maven just does. It creates a jar right now, a few years ago, a war. uh There are no no dependency and there are no plugins. So I don't need any plugins, because.

B

A

I just need a jar, of course um on for Azure functions, I need a maven, plugin and core, because I need the extension. But this is you know, are we?

A

Maybe you have one plugin and not not much more and um all the automation happens in cicd what means, for instance, if we need let's say we have a relational database, then we need to apply idb for for migrations, then, for me it will be a stage in the cicd pipeline will be not a maven task, um so Maven is built and uh cicd pipelines are automations.

A

Okay and um I fully rely on Maven conventions like you know, test for unit tests and it for integration for system tests so used to know standards whenever whenever possible, so our runtimes, um so actually everything is still absolutely uh interesting. We have bare metal, visualization containers and serverless functions and Eva you see this is the your question from before.

A

So um serverless doesn't have to be more cost effective uh one trick in all clouds. If you, if you use serverless for Enterprise applications, it is usually the cheapest way of running the systems. But if you uh use serverless, you are not using machines, so you are say: I just need. Ram and I need a CPU. The problem is, you cannot? You cannot buy the machines in advance, so sometimes it is cheaper to buy machines.

A

You know in three years in advance and then run a fargate or any other container orchestrator on it, but um in most cases I would say: serverless is the cheapest way or and in the most modern way of running things and the most secure way at at least politically. You know secure, because the cloud provider takes two responsibilities of patching the operating system. Patching the jdks or your only responsibility is to to create a zip and ship it and push it.

A

Okay and I have countless screencasts about this live diploma as Lambda. So I, don't like to repeat it right now. I just will focus now on the on the meat on the on the summary, so serverless with Java everything is available and what we use is really depends on the cloud provider service so mostly right now, I'm using uh just uh this stock jvm. Why? Because gravel VM optimizes only once and the uh the hotspot optimizes the entire time so over time you will save money, but with ground VM you get.

A

You know faster startup, uh cold start, which is also minimized by crack. So recently, oh recently, there was um there was um crackers. I I cannot remember the the acronym. This is uh resource at uh uh correct forgot. It uh restore a checkpoint on coordinated, restore checkpoint, crack, coordinated, restore a checkpoint and what it does it freezes the state of the jvm on disk and then restarts it very quickly, which is perfect for serverless and guardian just starts quickly. Correct, uh just restarts and goes to sleep quickly, and uh we you can use everything.

A

So what I? What I'm doing I'm using this Jet and I will use a crack called snapstart on adapts, for instance, right now and um and micro profile and Jakarta 80 just running on everything. Happily, so it doesn't matter and um also great Innovation, CDI light. This is actually the idea that um that you can optimize at build time and not a deploy time, also crazy idea and and a nice idea, pirate Cloud where they are running they're running pyara. In a cluster for you, so you ship a war and they care about your War.

A

It's also featherless, but completely different, actually different approach, which is but it's interesting test. Okay, so System test. First, in most Enterprise project, everyone starts with unit tests and the only reason what I, what I see is because, with a unit test, you get nice code coverage statistics which management cares about. But um you know just caring about unit tests is, like uh you know, building a airplane and just caring. You know about the radio buttons in the cabin and never flying it. So what we do is we establish.

A

You know Maven, build the pipeline System test first and because, at the beginning, there's almost no business logic. We are happy that we hit the end point and see that something happens. So we deploy our. You know our code and we would like to see you know that the entire pipeline is running so System test. First then, torture test I will see how the system behaves on the load and then on the um after a few iterations. You get more and more business logic and then we've write unit tests.

A

So you know my Approach is completely different. What you read in books, or or or or articles where you know test driven development, is unit tests, I would say at the beginning. There is no logic, you you're just exposing you, the entities via juxtures, and you are happy that you know the DNS is set up. Certificates are running, security groups are open, so this is actually the main concerned at the beginning. Now you can save a lot of time using micro profile risk client for testing.

A

So what you can do you can inject a Java interfaces, microproof, arrest interfaces and and call them, and the cool story is what you get then are tested micro service client for free. If you use rest assured or any other framework, you cannot reuse anything so you're. Just writing. You know your end-to-end tests. Just for the sake of testing with micro professors, client, you get high quality micro profile, clients which are usable you can you can. You can give.

A

You know your your tests to another project and they can reuse your system tests as the official microservice client. So we do it a lot um copy and paste from Jacksonville's resources to microproof, RS client, so an example, so a very simplistic juxto as resource by the way. This is from my GitHub project. This is later in the references from edible as London. Actually it looks like this, and um so- and this is just a copy- this is the micro profile.

A

Rest client, as you can see, it's a copy of this resource and um and uh in my in my system tests and then I can inject with Corpus test. Let's say: there's an example is cochle test. I can inject this greetings resource and just you know test my endpoint and the cool story is uh this: is the uh the environment, entry and the environment entry can be overridden in the pipeline, so in the pipeline I know my DNS names. It is overridden that I'm calling the external endpoint.

B

So this is all my projects.

A

Looks identical regardless of of environment, so um we can reuse it in the interfaces and another trick is, if you put this greetings resource, microproof, RS, client to Source main Java.

A

You can actually build mavenclean package or deploy the system tests and it will create a jar with all your interfaces, and this is your official becomes your official micro profile, RS client and by the way, I use the same interfaces for stress for stress test as well. Okay, so um what happens? Then? It really depends on the project, but sometimes we build on the you know. Micro professors, client interfaces so create a nicer way with Builder patterns, whatever to test the project and save even more time exactly so.

A

um This is the session 10 years after from java A6 to Corpus, and they are the projects and we have five minutes left. So um you can ask me, questions or uh I'll show you my old project. So if our, if you have questions now, it's time to ask yeah.

B

So I I don't see any questions uh coming in uh right now. Do you have a question that they should ask you.

A

No I think whatever I said is uh no self-evident, so I would say yeah because there should be no questions left. This was just no that's the spirit yeah.

A

This is an 11 all years old project, um so I I already migrated it to Corpus. It was like you know the um the hit statistic for my blog and um and uh if you take a look at this, this is the boundary control entity hits. So there is a hits counter country um entity. This is how it looks like Imports. It is on on on GitHub I problem. I have in most projects, I have ndas.

A

I cannot show you something from production, so I try not to find something which I can share with you, so logging, so that we have several logs in in boundary statistics um we have a daily statistics resource which is Jax arrest, which hits per day. This is yesterday today or whatever um we have the control, which is the.

B

A

Application scope gets injected with an x-ray log, as my logger, which I hope this is an old code, so 11 years old, but it uses what Java UT logging. So I was a little bit afraid not that I'm using log.

B

For J but Java logging.

A

What I use right now is Java. System logo is even lighter than this one, but I did it. You know 11 years ago, and it's still the same code. We have the entities which are um yeah exactly not persistence. In this particular case it was Jax B uh right now, I will use Jason B.

A

Yes again, this is old code and I use back then Jack SP to to create a Json format right now, I would use jsonp or Json B what it depends on the flexibility if we have a node to ship multiple versions of an API at the same time, I use jsonp, because it's easier to have you know in the new version there are new attributes in the older version. There are not no attributes.

A

If you use Json B, which is a Java class which is annotated, you get a problem that is really too hard to differentiate between not existing, attribute and attribute, which is null, for instance, right. Okay, so.

B

Adam, we have a question for you very good. Yes, and that is what is your opinion on on JSF or Jakarta faces uh in a project.

A

I I would say with something like Prime faces, still highly productive, so uh it is a little bit um out of fashion, but um you can be very productive and you can you know ship very quickly with JSF. The only problem is, if you are in the cloud just have a stateful, so you should be able to configure the load balancer properly because I always with the session ID you should hit. You know the same, the same, uh the same node.

A

If you are on uh fargate or container content applications, you can absolutely do this um in Lambda is harder. I think it is not. uh It was hardly with Lambda. You cannot do this and this is cost again with JSF. You will probably need a server which runs the entire time, so uh you will have to pay the entire time for GSF on premises. That's our problem right and um but we we had that discussion a lot, because uh GSF is a server-centric framework. So what it means is um it was Data binding.

A

So it is. It is really easy to have forms complex forms with validation with JSF. Jsf is less suited for uh offline apps, of course, and with web components, for instance, you can build uh offline apps, but if you have complex forms you will have to validate twice in front end and in backend. So this is my opinion about GSF. So.

B

So Ariana chimed in that the faces actually has a stateless mode as well. So.

B

Another thing uh have you ever brought in in in in Jews, uh rather than CDI, or what's your what's your take on Jews versus I'm, not sure Jews is ever even maintained.

A

Anymore, but uh yeah um I used a juice. I took a look at juice at the beginning, I didn't know, I, never liked that, and the reason is Jews didn't support it. Conventional configuration as I remember with juice. You always had to do like interface binds to impul, and this is what I said: okay I'm, too lazy for it. You know if you use welt or whatever we had, you only had to say at inject an interface.

A

If there's one single Implement worked, which Jews I have to express explicitly say, you know Iran any any other questions, because I'm running out of time, I think yeah.

B

You are so so there are some other questions, but I think they are uh probably better suited to one of the sessions that are coming later. Oh.

A

Okay, but I want about this is my. This is my only session. Hopefully, yes,.

B

It's your own okay, I was.

A

Sweating already it's like noted.

B

No you're online in in 15 minutes with the next session yeah.

A

Okay, no, don't worry.

B

uh This is your final sessions.

A

It is okay, very good, so um my policies.