Видео

very impressive, but Vaadin...

This is just amazing! I love it

We used retrofit client which is completed annotated interface has configuration in properties files and it does not need any implementation.

Looks really cool! Would it work with kotlin and ktor or is it java + spring boot only?

Wow.. This is amazing.

I disagree, I see developers having difficulties with a single stack of development, to follow its evolution, much worse trying to follow the evolution of several stacks. More old are you then less time to study and research.

I've never found a way to view groups of projects separately. That is, I'm working with projects from Group1 - P1, P2, P3, now I would like to work only with projects from Group2-P4, P5, P6). I would like to switch between them like in other IDE's

This thing is best bro. You guys have any intention of RSC support??

Hell, I like "verbosity" of old UI

Waiting for ...open feign🎉

smooth

Speaking about front end, It would be nice if Spring team is able to allocate the time and resources to implement InertiaJS adapter for Spring.

Nice Talk👏

"Key Promoter X" is also very good plugin. It will tell you the exact shortcut for an action you performed using the mouse.

I feel this approach a bit confusing especially when you pass repository into the domain entity. What can be more straightforward than having 3 main layers (Controller, Services, Repositories). In real life scenarios, there might be a lot of communication with different systems, so putting all that logic in service layer looks more reasonable for me. And basically these UseCase classes could be in fact small granular services e.g. AddBookToCatalogService.

An amazing talk, thank you. Yes the bbq pics were a bit distracting through novelty and perplexity but I did manage to just think of array box representation instead. But the content is great. It’s always good to have a JPA refresher. 🎉

He's the right trainer for my Brain at gym.

I don’t get why people hate Spring Security. Whenever I learn a new language, I wish it had something close to Spring Security.

nice presentation, mr. homelander

That's actually a really nice presentation! Thank you very much! I like the examples and how they are structured. To be honest, even after working for many years with Spring and Spring Boot, I wasn't aware of some of these hints provided by Christoph!

Great to see at 08:43 that Spring will take up EE 11 APIs!

Great talk!! so much learnings and addressed real life problems I faced while writing background scheduled jobs... btw we used ShedLock library but this is real good insight.

Ah, yet another Order and LineItems example. Very creative from Spring experts in this year's Spring I/O.

top talk!

Great talk, but still don't see any chance to use this in real world biz logic. For example: It do valid in domain object, but what if I got a new requirement that I need bypass or add some valid in some biz logic? It seems hard to do this new task. Instead, with old school POJO way, it's easy.

Wao! What a great presentation, thank you Ivar Grimstad.

Great

This might looks fancy but In my work experience, this way of modeling microservice is worst thing you can do in fast developing world. I want my developers to get features out as fast as possible with proper testing. I don't want them to waste time in managing packages. controller, service, entities, repositories, util, helper. with No shitty one interface, one class thing. just keep it simple !! You are not gonna need it.

It's a lot of tricks to implement to make Java performs well in Serverless context. Rust ?

Sorry people, but the presenter has thought about a pattern to get the point across, it may or may not be what your expectation of a perfect presentation is. But still good to give some polite feedback. Thanks for presenting and making it available for us. Some really good takeaways..

Congratulations on your presentation! You absolutely nailed it. Your thorough research and confident delivery captivated everyone in the room. Your ability to explain complex ideas so clearly is truly impressive. Keep up the fantastic work!

Some of the slides in this talk were downright terrible. Like, the whole BBQ section. Why would you fill your slides with 100% irrelevant BS instead of a single example or interface definition? How does the viewer actually implement any of the ideas mentioned there using Spring Data? I presume typing the name of skewer in my IDE would not work. I get the idea of trying to give a fun theme to your talk, but don't let that fun be at the expense of the viewer.

Quite interesting talk .. excited

I migrated a medium sized project to spring data jdbc and was impressed by how straightforward it was. Sure there were some things that had to be changed, ran into a few footguns along the way, but in the end it simplified the code and opened my eyes to all of the "magic" that was happening behind the scenes in the JPA implementation.

Great Job Cora Iberkleid, very nice presentation. Even though the IDE has given you a hard time, you've handled it very well.

I'm a simple man. I see Josh Long, I click the video

Can it work in distributed deployment? Like EKS.

Great presentation and confidence

This talks is excellent and it has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats Maciej!

simply schauderhaft

what's the difference between reading and writing with a rabbit or kafka and reading and writing with a database? Usually i'm using REDIS for solve same problem, because it much faster than usual relation db

I did not understand how the openApi spec was combined and created on gateway side, i understood that the routes are configured on the fly. Could someone answer my question?

why the edpoints could be private?

In my opinion, the domain shouldn't know anything about how the entity will be saved, updated or whatever, and where it would happen. For the domain it should be an abstraction. For example, you can decide not to use JPA, and use JDBC instead. And if you're designed your application correctly, you won't change anything in domain module, you won't even recompile it, and only persistence module will be changed. And modulith only help you design you monolith application, not microservice with DDD. But gradle can, since for each module (presentation, persistence, use cases, domain) you can set it's own dependencies. And, for example, domain will never depend on use cases, and you can even write tests for that. And you don't even need to recompile inner modules, when you change anything in outer modules.

record BookId(UUID) record ISBN(String) .... These wrappers create more tasks for the GC. I'm waiting for the day when the Java compiler supports new type/opaque type like the Scala compiler (i.e. we still have BookId and ISBN but the compiler will remove them while still keeping all the validations inside them).

Nice explanation! But did not cover very important case if your app has more than one job marked with @Scheduled annotation. Because it may be crucial moment of performance. May be it will be covered in next topics.

Muito bom!

Thank you very useful

Great example. I have continually searched for how to use Spring JPA in conjunction with DDD, however, I always felt like I was encountering too many violations. Your approach manages to keep those to a minimum so I will certainly reference this demo moving forward.