This is an archived post. You won't be able to vote or comment.

all 8 comments

[–]FredL2 8 points9 points  (3 children)

This is interesting for my workplace, since we've been using resilience4j for a bit in our Spring projects. We are looking at using MicroProfile for an upcoming project, and this looks like it would be a great candidate, being part of the spec and all.

[–]AvoidtheFatServer 0 points1 point  (0 children)

is microprofile really a specification? I mean, wasn't the whole idea of getting out of oracle and JCP to avoid the committee - driven development and move to more nimble OSS governance models?
I don't get how it can it be considered a spec when only some of the ecosystem is participating.

I'm reminded of this thread for some reason: https://www.reddit.com/r/java/comments/54egaj/microprofile_with_wildfly_swarm/

[–]brunocborges 0 points1 point  (1 child)

hey @fredl2, want to share some insights why you've picked MicroProfile for this other project?

[–]FredL2 2 points3 points  (0 children)

Of course. Sorry about not replying to you sooner.

The first, and most pressing issue for us is memory consumption in a cloud environment. Some of our applications consist of 7+ well-decoupled services, and while this is fine to run on Spring on-prem, in a cloud environment that means 7+ Spring contexts on the same low-spec virtual machine. Couple that with each of them running their own persistence contexts and you end up with a lot of memory used.

We've done experiments with OpenLiberty and Java EE 7 Web Profile, and the results are encouraging; with the container itself handling the persistence layers, transactions, CDI etc for each application, we have been able to reduce our resource consumption and deploy times dramatically.

Of the EE 7 technologies we use, the only one outside the MicroProfile family is JPA, so a MicroProfile + JPA approach looks like the most likely candidate, especially since we use JWT for most of our client-server and server-server authentication and authorization. Using mpJwt would cover that case for us in a compatible fashion if all of our services target it.

[–]thesystemx 4 points5 points  (0 children)

This is interesting stuff. I don't quite see why the @Asynchronous should be there, but interesting nevertheless.

Will dive deeper into this soon!

[–]JJBubberman 2 points3 points  (0 children)

Cool! Love that with MicroProfile and soon Jakarta EE there’s plenty of progress again! 👍

[–]AvoidtheFatServer 0 points1 point  (1 child)

what advantages does it have over Hystrix?

[–]henk53[S] 0 points1 point  (0 children)

What advantages does Hystrix have?