the only thing i absolutely hate about java is the lack of async await reactive programming is not nice to work with in java reactor

Any buddy help. I get empty list in postman response when i mapping model class to dto build using spring native build and build use jvm it works...🤔

awesome explanation of virtual threads !! thanks for this :)

TIL ApplicationModuleTest. This is what I was looking for for so long. The vertical slices that allow me to focus my tests on a single module. Great!

There is something codesmell I think. Domain layer should be written as pure as possible. Repository definition and entity definitions violate something here.Tests of the domain layer should also be written independently. But there is JPA dependency here.

Regardless if you end up going with Spring Cloud Gateway, it is a great way to your head around the nitty-gritty of API Gateways.

so all the control/validation/restrictions/events will be in an Entity/POJO, services and business layers are empty :/ ... you manage the entire flow of a project by the actions performed against "the domain"

So much information was conveyed in a single talk. Fantastic presentation!

Jesus Christ, we have SQL, why are people so obsessed to complicate things so much. They literally created a thing that replicates SQL when we can just use SQL and map the result to a class

great talk is it possible to get the vite + spring repo for reference?

Essa abordagem serve para todos os modelos de banco ou há algum diferencial entre eles por exemplo o Oracle?

I built my business on spring, couldn't have done it without all the open source community

Hmm I did not get this topic. JPA is ORM, Object-Relational Mapping . Some implements JPA because we want to look all tiers including DB/table part as object view. I feel he is trying to do JDBC as ORM. I would consider DAO pattern to solve it. Nothing right or wrong, it likes EJB, CMP vs BMP.

normal people at 5 am: sleeps devs at 5 am: watches this video

Is it possible to use Spring AI with local LLMs using Ollama?

If one uses jpa entity classes that need mapping to domain objects there will be quite so code gymnastics to lazy load collections because mapping them will always result in an eager fetch

I feel like if I found a treasure

Thank you for the insightful talk! I appreciate the points made, but I respectfully disagree with Oliver’s statement around minute 17 regarding the necessity of using jMolecules to define aggregate roots. In my experience with Spring Data JPA and Domain-Driven Design (DDD), we can effectively define aggregate roots by leveraging the `AbstractAggregateRoot` class provided by Spring Data, without needing to rely on jMolecules. This approach works well for managing domain events and maintaining the boundaries of the aggregate in a clean, straightforward manner.

❤❤❤

This little maneuver is going to set us back 15 years..

please share code link

Interesting but Domain driven design I still don't get the benefits on micro services at least. A lot of classes and complexity. Yes small classes are simpler to maintain. Anyway I will continue the journey with the videos you mentioned.

I would say this talk is great for beginners. He explains the subject very well but you'd already know most of the stuff he talks about if you've written tests.

❤❤❤

I tried learning spring Security via doc and it was terrible hahaha 🤣 I got a tutorial on the internet from amigoscode and now I advocate forthe usage of spring security

❤❤❤

Is this on production now, and where i will get that what i need to add in pom.xml file what are those

Really Helpful :)

I really enjoyed the Video but did anyone tested it? Note I like the concepts provided and agree in most of them but checking DomainEventListener located under application or Catalog module fails modulith verification with the LoanCreated and Closed events from Lending module: - Module 'catalog' depends on non-exposed type library.lending.domain.LoanCreated within module 'lending'! LoanCreated declares parameter LoanCreated.handle(LoanCreated) in (DomainEventListener.java:0)

As a side note, the original example program has one further problem which wasn't discussed - if the job runs every 60 seconds, what happens if it takes more than 60 seconds to complete, giving you unintended parallel processing? I've been bitten by that one a few times...

Does spring security has support for webauthn now?

That was a great presentation. learned a lot

Great video! Under the heading of "more functional" I do wish Urs had mentioned the fact that many more things are expressions in Kotlin than in Java. For example, try, if, and when among others all return a value. This eliminates the all-too-common and error prone pattern of creating a local variable initialized to null upstream of a block, and then assigning to it inside a conditionally-executed block. Instead, the if/else or try/catch itself returns a value. This contributes to concision, safety, and readability.

That remove example was bonkers! using lists should not have that much of a performance penalty!

spectacular explanation with clear and simple to comprehend demos

it was so good. thanks

This is truly and event sourcing revolution. The condictional append is better than just enabling multi stream transactions at the persistence layer. Thanks Sara Pellegrini and Milan Savic

36:48 Actually in our example, each instance will fight for first 50 records, not one record as it is illustrated in the slide.

26:34, 31:59, 32:14, 36:04, 40:31 - key moments

Ola. Todo bem

Very good presentation 👏correct me if I'm wrong, but for the issue at minute 30:58 a simpler solution would be using @MockBean Clock clock;

I love this man soo much.

How to use it with Hibernate 6? LockOptions.SKIP_LOCKED is deprecated

I found the idea of coding the implementation as userstories / usecases extremely insightfull, seeems to work really well with ddd. Goes hand in hand with good architecture documentation and requirements engineering and is pretty good from a perspective as "code as documentation". Never thought of this. Its roughly at timecode 34:30

25:27 DDD code review. - You don’t need to RE-validate the ISBN value object. - Domain coupled to infrastructure (framework)

Good Job 👏🏽 helping and empowering Spring Developers. Just to point out to think our decisions. 24:12 Domain coupled to infrastructure. - You can not port this domain to other framework. Trade off or Smell ? You could dispatch a domain exception. `InvalidBookIdException` and get rid of the framework dependency.

Very good! thank your for the valuable content!

So according to Josh, we should have everything in one package/class(controllers, services, repos)???? Let him show us the real-world scenario first

Amazing persentation, very usefull, thanks Rafael!

Nice approach to make full-stack life easier.