Spring Tips: Spring Boot 3.2

Hi, Spring fans! In this post, we're diving into the cool new features of Spring Boot 3.2 and Java 21. We'll explore how virtual threads from Project Loom make your code run better and how Java 21 enhances your applications. Plus, we're building a Java 21 program right here! We'll talk about how SSL support and improved observability in Spring Boot 3.2 can help you in production. We'll also look at the new Project Loom and Project CRaC support can help you go faster with less work. You'll learn about how some very nice features in Java 21 - sealed types, records, pattern matching, and smart switch expressions - go hand in hand with production-ready services. Get ready to see how these updates available in Spring Boot 3.2 can make your developer life easier and more efficient.
#Java21 #SpringBoot #SpringBoot32 #JDBC #REST #HTTP #ProjectLoom #HTTPS #virtualthreads #security #sealedtypes #patternmatching #SSL #softwaredevelopment #programming #code #efficiency #observability #technologyupdates #Java #GraalVM
code is here: github.com/spring-tips/road-t...
make sure to check the `README.md` here : github.com/spring-tips/road-t...

[@LukasBradley]

Please use Chapters on your videos. Thanks!

[@joachimdietl6737]

like they do in the motorcycle club?

[@jamesrooney931]

0:01:04 Java 21 & Data Oriented Programming 0:11:27 Virtual Threads (LOOM) 0:28:40 JDBC Client & REST Client 0:44:18 Co-Ordinated Restore at Checkpoint (CRaC) 0:57:20 Better Security with SSL 1:05:14 Observability

[@nikhilvijay6022]

Doing God's work

[@umutylmaz7800]

Great video Josh thanks! I'm leaving below the topics covered in the video. 0:00 Introduction 1:00 Data Oriented Programming 11:25 Virtual Threads 28:40 Jdbc & Rest Client 44:15 Coordinated Restore At Checkpoint 57:16 Security With SSL 1:05:10 Observability 1:21:01 Onward

[@florianpopa8848]

Thank you for sharing this! Having worked as a PHP developer for six years until 2018, I've experienced its limitations firsthand. Since switching to Java, I've found it to be a significantly better experience.

[@chandanveeppa8081]

Powerful content! Thanks a lot for putting so much effort into creating this demo. Saves us developers a ton of time skimming though all those reference docs and release notes. Good to see Spring getting so many useful and interesting features.

[@arnaudpoutieu1331]

Many thanks for your energy and sharing such passion with us!

[@bentobei]

Thanks Josh and everyone involved! Valuable tips.

[@kenwang8595]

Great video! Just in span of one hour, I feel that I have learned so much! Many thanks!

[@DanbyArg]

Thanks for all of the great content Josh 👍

[@nagamohank2244]

Thanks! Josh for the Tips

[@Mateusz-xr9qw]

That was very great start of a day. Awesome video ❤

[@SumitSharma864]

Thanks a lot informative and useful video. Really helpful to understand whats new there before upgrade.

[@joachimdietl6737]

Josh you are the best! And of course we want the new JDK request factory, so let'S say new blablabla very good!

[@saintpaulbassanagavi3]

Incredible video

[@javisartdesign]

thaaaaanks! greatest tips ever

[@javaspringdev]

Thanks Josh that's a great video

[@bawaparampreet24]

11:27 : Virtual Threads 28:35 : Jdbc Client & Rest Client

[@MarianSchubert]

Thanks!

[@konstantingromov6485]

Josh talk is great as usual. One small thing I've noticed - why @Controller+@ResponseBody but not @RestController in demo examples?

[@coffeesoftware]

because what Im doing isn't REST :) it's HTTP with JSON. If I used HATEOAS and hypermedia, then it'd be proper REST. it's also more consistent with RSocket, GraphQL, web sockets, MVC, etc., uses of `@Controller` in the rest of the stack.

[@pouyakhoshkhoo3855]

Thank you

[@CheeseStickzZ]

23:56 This made me giggle for a whole hour. I agree Php is the biggest mess in the history of web development

[@DenisKorolevR]

Thank you for your video! But it looks like that Sleuth in Spring Boot 2 was easier to work with.

[@vukotici32]

set('springCloudVersion', "2023.0.0-RC1") i am sad to see that the sprng cloud version is not ready for spring boot 3.2 we can not update

[@karthiksundaram544]

❤

[@mycode0]

woww Java has changed a lot

[@hobaca1465]

Interesting KZbin thumbnail - String Boot and SSSL... all good, midjourney still has aways to go.

[@asishkumarsatapathy3466]

Chapters please sir... Anywau thanks for awesome content!! Cheers 🍻

[@vishnuvs6121]

Did you use ChatGPT to generate the thumbnail?

[@chrispure7461]

oauth2 token/refresh suport for restclient?

[@marcinkunert]

Is there a way to prevent data.sql / schema.sql being run on restart? Similary to what @RestartScope does.

[@Gohel95]

Hey @josh at 36:00 you use @Responsebody and @Controller is there any reason for not using @Restcontroller?

[@coffeesoftware]

well spotted ! the reason is because... it's not REST :) I'm not actually using hypermedia and HATEOAS and the like. I'm only at level 2 on Dr. Leonard Richardson's Maturity Model. I got tired of having to juggle that conflict in my head and I embrace the reality: it's just an HTTP + JSON endpoint. Also, Spring has a ton of uses for @Controller. It's just more thematically consistent to use it all over the place. If there was a `@GraphqlController`, and an `@RSocketController`, and an `@MvcController`, etc., then maybe I'd be more inclined.

[@Gohel95]

you're a great man @@coffeesoftware. Thank you so much for the explanation.

[@avalagum7957]

Does Spring Boot 3.2 give us a VirtualThreadPerTaskExecutor bean or do we have to create one?

[@hendisantika]

Like this: spring.threads.virtual.enabled = true

[@avalagum7957]

@@hendisantika did you really read my question? 🙂

[@avalagum7957]

Answer to self: no.There's only 1 bean of type Executor in the Spring application context. When a runnable, which prints out the current thread name, is run by it, it prints out something like task-1. The thread used by Tomcat in spring webmvc is a virtual thread (its thread name is like VirtualThread[#73,tomcat-handler-0]/runnable@ForkJoinPool-1-worker-1). That means there's no need to create a VirtualThreadPerTaskExecutor in a spring boot based web app.

[@kennethcarvalho3684]

Problem in IT field is information overload. How can mind keep all this information

[@TaiChiSWAG]

until one practically apply one of the new features

[@user-hp6gf7lu8c]

Don't be overwhelmed. Instead, you have to decide which core information you must need and most probably learn it from an official doc or book. Because from reading, you have your available time to consume the information in your way. But in video, you have to follow the creator's style of timeline to consume information, which in most cases won't be within your required time demand.

[@kennethcarvalho3684]

@@user-hp6gf7lu8c thanks

[@salo.]

Can I use Graal with default JDK 21? OR I should always download and set Special Graal 21 JDK ?

[@coffeesoftware]

you need the special GraalVM (or Liberica NIK) distribution. It's amazing: Java is an open source distribution. GraalVM is a fork of OpenJDK with some extra features. There are many OpenJDK distributions, GraalVM is but one of many. But did you know that GraalVM itself has forks and distributions? Liberica NIK (from BellSoft) is one such distribution.

[@salo.]

I can't see the answer, somewhy.

[@WaterOfPanela]

why is gradle so overlooked?...

[@dimitricharles9784]

Php the 1 trillion dollar mistake 😂😂😂😂😂

[@lompatin]

String boot?

[@rtb8085]

I think you have a bit of confusion about the meaning of Tuple conceptually: tuple is a pair, and not a container for single element !

[@maksimmuruev423]

Testcontainers support is kinda bad.. you have to put those lines for container control in each test suite.. is it even wise? I mean test itself probably should not care about which db connection in use embeddeddb or docker.. also conversion from embedded to testcontainers is painful in this way. I've found a way do it without update each single testsuite but its kinda hack anyway. Will be good if spring boot allow this just setup in separated config file or maybe just one annotation in testconfig..

[@shelajev]

Modern Spring Boot does include exactly that. You can declare Testcontainers containers as beans, so their lifecycle is handled automatically, use `@ServiceConnection` annotation to automatically instruct Spring Boot to use the annotated bean as the default datastore or message broker (there's a whole set of supported technologies) so the connection details are handled automatically too. You also can put the container beans in a @TestConfiguration, and instrument your test classes with using that without changing the tests themselves. And you can even run the app itself with this configuration, so you get the environment for the development setup. Here's a video where we explored these concepts: kzbin.info/www/bejne/bZqTdJKHjNWGpJo

[@CheeseStickzZ]

I just came here to say I hate reactive programming with a passion, thank the heavens for project loom. Us old school java developers (8 years+) cannot stand the reactive paradigm

[@shakib_04]

thumbnail likely generated with AI

[@karthiksundaram544]

😂

[@KhodeCamp]

Thank you so much for the tips!

[@karthiksundaram544]

❤