golden stuff mate <3..

How come many ppl are already using SpringBoot 3.3. It doesn't even have Spring Cloud dependencies yet(2024 May 30). 🤔🤔

ok

let's go spring

Great Keynote and really eager to be able to use Spring Framework 6.2 and SpringBoot 3.4 by the end of the year :)

Oh so you make yearly releases! Is that something of now?

Please share me the repo

2023 after movie?😅

Amazing presentation!

half of the talk is “yeah”

Josh is in wrong profession , this cud be part time and standup comedy as full time. Amazing talk 👍🏻

I love this presentation! How to get the code and file on your presentation?

So many gems in this session! Thanks for sharing

23:42

Thanks Josh for the outstanding talk

Good information! Thank you

My go-to Spring conference in Europe 🍃

Carrying forward Ravi's comment- Can jobrunr work in a truly active-active setup? If I've 2 regions for resiliency, where jobrunr is setup - each region accepts 50% of job requests but database is shared by both regions. Can jobrunr guarantee exactly once delivery in that case?

Oh, guys, I read Iuliana's book, and I cannot recommend it. It has too much redundant and outdated information. She jokes that it's fluffy and you can use it as a weapon to defend yourself, but it only shows that she can't explain topics in a short and concise manner. Sorry.

Well, this is very basic. But such videos are also needed for beginners.

Thing I Wish I Knew When I Started watching: waste of time

Ok, I've read up on HTMX, and I get it. I've been developing for over 35+ years, and so I have seen this technology before as I remember Struts 1 & 2 and MVC and JSP and JSTL. I am sure you may not have been born during the DOT-COM days when everyone started to do web-development. Yes, HTML was great when the browser was the only consumer, but then WML came around and XML came around and mobile devices, and not just iPhones, but also Windows CE. There was a VERY GOOD REASON why we abandoned HTML as being the only data we sent out. Considering he MULTIPLE calls that could come to our controller, it made more sense to just send the data. If you know Spring Boot and Spring as you do, then you know you can send JSON or XML to the client, not just JSON. You probably also don't remember when every Network LAN Manager complained about sending/receiving too much data over the network and bandwidth was costly. Also, the time of loading pages was problematic at that time. I guess, what is old is new again. There is a fundamental REASON why we abandoned HTML to a client to begin with. I can't believe HTMX forgot that. HTMX won't be around for long when the 'geniuses' figure out why HTMX isn't a great solution to the world today.

This talk has a lot of subtlety to it under the hood. Unless you’ve been exposed to a Fortune 500 system or three, you might not be able to understand the reasons this works in practice. This particularly applies when making plans for decomposing a very large (4M-20M lines of code) monolith that’s older - where every change breaks something unrelated and every release is a buggy mess.

Does anyone know any video/textual course about how to generate OpenAPI Specification Programmatically for JAX-RS Web App. Please Please. I need it.

can you tell me how can i get the code in the video?

Apart from the great content, the presentation and the explanation were really great!

I disaggree, discriminator for Data Isolation is robust as long as the discriminator is a composite key enforced at the database level. I don't see how you can "accidentally" expose tenant data with this approach!

30:34 GraalVM & Reflection

Thanks a lot, it's the great session. I'm accumulate a peach of information from a lot VDO

Pretty bland overall, but you lost me at the telemetry.

nice sharing，learn a lot

Great job, old friend!

Amazing talk! Great information put out!

I am getting error while using BCryptPasswordEncoder instead of NoOpPasswordEncoder. It says Encoded password does not look like BCrypt.

That's a very nice tutorial, even 7 years later. Currently I'm trying to weigh out the benefits of using openapi vs test driven documentation, and I'm deffinitely willing to give Spring REST docs a try.

You saved my day, Thomas Vitale. Thank you so much.

One of the best presentations from Spring I/O 2023!

Help. It is statefull, isn't it?? because no sessionCreationPolicy configuration written. like customizer.sessionCreationPolicy(SessionCreationPolicy.STATELESS)

Nice

hi, did not find in application sources how traces delivered to tempo collector? Usually it should be defined in springs application property files in management or otel section.

Java 8 is part of the obsoleted knowledge economy.

This is great. I actually skipped over the best part (component-based architecture) while I try to ignore other architecture styles :). For someone in a hurry, it would be nice if it came first and other styles discussed last.

Just leaving a footprint to see who finds me from this neck of the woods

Thanks for the talk, I'm curious . In the presentation you have mentioned e.g. a feature library (s3-property-sync). What are some more examples of libraries you maintain for the teams? Are e.g. the "core functions" parts going more into the core business models/data/logic/data-sources?

Not very impressive.

77 megabytes is "small" 🤣

KeepGoiing Spring i/o

For API's you said access_token, but we have API keys also. When should we use API keys instead of access_token? Can you please help understand?

This is damn great and the speakers are cool

This is gold! Thanks!