Your new subscriber ❤🎉

That's very helpful, I like your videos 🔥

Thanks man. Pretty nice content!

Thanks for bringing great and simple examples to things sometimes kinda "obscure" like @Transactions!

learn a lot thanks for the explanation. I have subscribed and hit the like button

Great Explanation!!

Top video. Didn’t understand the annotation until this!

@devolajide

Жыл бұрын

Same here. I use it but I don't understand it and I have been asked in interview before.

great job. keep the good work !

better use case and good delivery. thank you for this atomic featured videos. it will change the way we knew about what we already knew. it's great please put this video in to a atomic features playlist.

helpful content, thanks

great explanation ❤👍👍

Great explanation, as in your other videos.

may be you can add introduction to the Saga pattern for distributed transactions and how to use it in Spring Boot app ?

Do i need to add Transaction Manger @Bean in the @Configuration class or is it autowired for us with Mysql / Postgres dependency or something?

@devtiro

Жыл бұрын

Thank you so much 🙏

@ajs9721

6 ай бұрын

PlatfformTransactionManager bean is auto configured. So it will work out of the box, But like everything you can override if required.

Does @validate also make the action atomic? Does it save non-validated requests?

@ajs9721

6 ай бұрын

@Valid and @Validate are JPA annotations, so that is a different use case, and will throw exception at the controller during binding, won't even go to Service layer.

All well and good using this in your service layer, but how will this work with clean architecture? The service layer would be replaced by the Domain layer and we all know the domain layer has zero dependencies on any other layer such as the outer spring layers etc. How would implement transactional behaviour using clean architecture and even things like cascade?

@mrbmro3991

5 ай бұрын

Maybe a solution is to have the controller call a dumb Service such as PersonService which contains the PersonUseCase. When the client calls PersonService.save() the save() method within the PersonService will have the @Transaction annotation and then the next line of code within PersonService.save() will be personUseCase.execute(). This way we simply delegate to the usecase where the business logic lives and at the same time it is transactional?