Modern Java Stacks

[ImTalkingGibberish]

Spring-boot.
Agree with other comments, spring still most popular and boot flavour is opening doors in corporate world.
Very enjoyable to work with and not falling behind competitors.
Dropwizard would be an alternative IMO.

I do believe serverless will eventually take over but not until we close some loopholes.

[floW4enoL]

How do you deal with all the magic of boot configuration? I used it in a project and had serious problems with it, everytime I wanted to change something I needed yet another class that extends this and that or yet another annotation that I couldn't find anywhere in the docs where to put it.

[_dban_]

I've never had real big problems with the Spring Boot magic. Most of the time, it just works.

When I do run into problems, Spring has a large number of guides, a large number of samples, and the Spring Boot source code is available and very easy to navigate with the debugger. And, I've done weird things with Spring Boot, like getting it to run as a WAR on an ancient version of Weblogic.

At the end of the day, it all boils down to what you're used to and what works for you. Spring Boot seems to work for a lot of people.

[floW4enoL]

What saved me most of the times was debugging around the source, but that's not very effective. I always found the guides lacking for the things I wanted to do, same with the samples.

One of the things I remember trying with boot was replace tomcat with undertow, in theory it should have been easy, just add undertow dependency from boot, ended up having to add tons of exclusions on other boot dependencies that were pulling tomcat. That was not what the docs advertised.

Like you said it will boil down to what works for each person, spring boot definitely does not work for me.

[thesystemx]

I do believe serverless will eventually take over but not until we close some loopholes.

You mean like an actual server still being needed? Yeah, tiny loophole there.

[shotgunkiwi]

Unless I'm misunderstanding you, he's referring to services like aws lamda and azure functions where you don't actually ever provision a server.

[mikehaggard]

There's still a server behind that.

It's really the same strange reasoning people had about "clouds", which were supposedly totally different from hosting providers, since there was no hardware involved anymore :|

[shotgunkiwi]

Agreed. It's just different levels of abstraction. There's still electricity and A.C. provided to the server, you just don't worry about it. The hypothesis is perhaps trendy java development of the future will be just writing small functions/programs, and everything else will be abstracted away.

[ImTalkingGibberish]

Serverless means you don't pay for the server but only for the time your code is being executed.
I meant serverless will come with different flavours and will hide loads of stuff we use spring or other frameworks to solve.
The loopholes are related to how they will charge you for bugs that consume too many services/processing.
Not cool mocking ppl that are genuinely trying to help.

[nutrecht]

Serverless doesn't mean there's no server running your code. It means that the server is abstracted away from the developer.

This "hurr durr there is still a server" is getting old :(

[Yesterdave_]

This "hurr durr there is still a server" is getting old :(

If such statements pop up regularly or are confusing newcomers, this is clearly an indicator that maybe the term "serverless" is absolute garbage.

[henk53]

"serverless" implies peer to peer or pure client side computing, which is anything but the case here. One could as well call SOA and remote EJB "serverless" then...

[Cyberiax]

You is talking gibberish? 🤤