This is high quality content as always. Even I am familiar with the concepts and approach , ALWAYS there is a hidden gold 🌟 for me. In this video it was the @Transactional with Order saving & Event Publishing. Learned that event can be saved to DB and triggered using scheduler and this guarantees the expected Transactional behavior. Thanks Siva !
Sir can we keep the publishing logic at the end then problem sloved right save the data in database and publish and return correct me if i am wrong? Problem will be happen if we have publishing logic first after publishing if we are doing save at the end then we will have problem right but in the above we are writing after the save operation right if any exception occurs during save then directly control goes to exception handler right
@@sivalabsin that case we need to use outbox pattern which u have suggested above we need to save the event which need to published in the database so that if broker is down (sending message is failed) we can do retry later understood the problem sir
thank you siva, any video about database shema migration inthis project ? this is something than happen in real project, and we don't find enough high quality videos about best practices
Hi Siva, awesome work by the way. Keep it up, this definitely helps alot. 😊 I wanted 1 suggestion, i am integrating spring data elastic search and have created variety of different queries wrt to crud operations, range selection, I wanted to kniw where can i get reference to the aggregate queries for the elastic search version 7+ and spring data elastic version 3. It seems thay they have deprecated aggregation package and abstracted out with nativesearch. Any direction is really appreciated
Hi @SivaLabs , when this project is fully completed? so that I can buy membership and complete entire project in one go, because currently I'm preparing for switch and planning to put this project with all tech stacks in my resume.
Except the last "Grafana Stack Monitoring" part, all the other videos are already available for people having Membership. This last part will be uploaded by end of April.
Another alternative to Scheduled and Shedlock is to use a Kubernetes Cronjob. Although, that option creates a security question on how to expose an internal webhook trigger endpoint that is secure and only allows internal requests.
This is high quality content as always. Even I am familiar with the concepts and approach , ALWAYS there is a hidden gold 🌟 for me. In this video it was the @Transactional with Order saving & Event Publishing. Learned that event can be saved to DB and triggered using scheduler and this guarantees the expected Transactional behavior. Thanks Siva !
Good you did this, recently faced this issue when I was practicing with sagas,
Awesome video!
Sir can we keep the publishing logic at the end then problem sloved right save the data in database and publish and return correct me if i am wrong?
Problem will be happen if we have publishing logic first
after publishing if we are doing save at the end then we will have problem right
but in the above we are writing after the save operation right if any exception occurs during save then directly control goes to exception handler right
how problem will happen if we are publishing after save method pl explain sir ?
Once the record is saved successfully in DB, and then the sending message is failed, then how to handle this scenario?
@@sivalabsin that case we need to use outbox pattern which u have suggested above we need to save the event which need to published in the database so that if broker is down (sending message is failed) we can do retry later
understood the problem sir
thank you siva, any video about database shema migration inthis project ? this is something than happen in real project, and we don't find enough high quality videos about best practices
Hi Siva, awesome work by the way. Keep it up, this definitely helps alot. 😊
I wanted 1 suggestion, i am integrating spring data elastic search and have created variety of different queries wrt to crud operations, range selection,
I wanted to kniw where can i get reference to the aggregate queries for the elastic search version 7+ and spring data elastic version 3.
It seems thay they have deprecated aggregation package and abstracted out with nativesearch.
Any direction is really appreciated
Hi @SivaLabs , when this project is fully completed? so that I can buy membership and complete entire project in one go, because currently I'm preparing for switch and planning to put this project with all tech stacks in my resume.
Except the last "Grafana Stack Monitoring" part, all the other videos are already available for people having Membership. This last part will be uploaded by end of April.
Another alternative to Scheduled and Shedlock is to use a Kubernetes Cronjob. Although, that option creates a security question on how to expose an internal webhook trigger endpoint that is secure and only allows internal requests.
Hey Thank you, can you please elaborate and give some example link so that i will implement in my project