Great work, few observations here. 1. You can create a common module to have all dto classes and reuse them. 2. good to capture order quantity for a specific product for inventory availability check and calculate the overall amount.
If database failed then data will be not inserted then in the next MS not able to get the data. So the order will re try. if Kafka fail then next MS not able to pick the record from db so the order status will not changed. So retry will be trigger.
@@JavaTechSolutions But, there is no distributed transaction between Kafka and the database, so if an error occurs, there will be cases where either it has been persisted in the database and not sent to Kafka, or it has been sent to Kafka and not saved in the database
@@JavaTechSolutions IMHO, i think it's a flawed design because it leaves the door open for the arrival of an order operation, and yet, the saga has not recorded that step. Until the Kafka library supports participation in 2PC (KIP-939), it would be necessary to implement a transactional outbox. Even in my opinion, if they were to implement it, it should be designed that way.
You could have explained more about orchestration service instead of spending more time on other services. Also, instead of typing the complete code you could have the code already and just walk through the code.
Can you a video on spring security with jwt token and password should be encrypted in the database and also also user registration successfully then a message send to user registered email.... The registration field are username, email id and password... Please urgently need it .. please
Hi sir, I gone through the choreography approach was really good. But this video contents are good but explanation is less Very Hard to understand for beginners. Thanks.
Sorry but the explanation here wasn't the great one. Just a suggestion try using some diagram or flow diagram to explain stuff before writing code.for that module.
Great work, few observations here.
1. You can create a common module to have all dto classes and reuse them.
2. good to capture order quantity for a specific product for inventory availability check and calculate the overall amount.
Thank you for pointing those things. I created this video just to understand the concept. Those are obviously nice to have. Thank You
Great content!
Please keep on posting these videos!
Subscribed
Thanks
Great !! Thanks
Thank
Really great content, appreciate it
@@jampanisuresh4457 thanks
Source code link updated. Please get it from description section
Thank you! Would love to see a spring batch app with orchestration if you have time.
Great suggestion!
Nice video. Is that right github link? cause I don't see the service like on the video
I will check the link and update accordingly
@@JavaTechSolutionsAny update?
@@hendisantika sorry to not updating... Actually I am sick from last 3 days.. once I will recovered I will update the link
OIC. Get well soon@@JavaTechSolutions
Updated
If the sending to Kafka fails, how do you maintain the transaction between the database and Kafka in the OrderService::createOrder?
If database failed then data will be not inserted then in the next MS not able to get the data. So the order will re try. if Kafka fail then next MS not able to pick the record from db so the order status will not changed. So retry will be trigger.
@@JavaTechSolutions But, there is no distributed transaction between Kafka and the database, so if an error occurs, there will be cases where either it has been persisted in the database and not sent to Kafka, or it has been sent to Kafka and not saved in the database
@@gonzalop6230 yes .. that I was saying...
@@JavaTechSolutions IMHO, i think it's a flawed design because it leaves the door open for the arrival of an order operation, and yet, the saga has not recorded that step. Until the Kafka library supports participation in 2PC (KIP-939), it would be necessary to implement a transactional outbox. Even in my opinion, if they were to implement it, it should be designed that way.
That can be managed in other way... Like by retrying transaction after certain time
Hi Thanks for the great content. I dont think you have the correct git link for the project. could you please provide the project link
Thanks you for your concern. I will check and update the link accordingly
Updated
Hi Thanks for the great content, just a request if you can make similar vids on Spring web flux would be helpful!
Sure will do that
You could have explained more about orchestration service instead of spending more time on other services. Also, instead of typing the complete code you could have the code already and just walk through the code.
how do we send user details to this system, knowing who is doing this request
Can you please check my jwt related video
thank u
Mentioned not
Hi, thx for good vide , but Github link is different from video code! can you update it?
Updated
Can you a video on spring security with jwt token and password should be encrypted in the database and also also user registration successfully then a message send to user registered email.... The registration field are username, email id and password... Please urgently need it .. please
Already I provided jwt token related video. Please check it out
@@JavaTechSolutions can you please share the link please
Hi sir,
I gone through the choreography approach was really good.
But this video contents are good but explanation is less
Very Hard to understand for beginners.
Thanks.
Thank you for your concern.. I will try to put more details in my next tutorial..
video is good but the main saga orchestration service is not explained well.
Thank you for your concern... In my next one of my video I will try to explain on this
Sorry but the explanation here wasn't the great one. Just a suggestion try using some diagram or flow diagram to explain stuff before writing code.for that module.
Noted!
i have app which let information to the next person
Not clear to me what you are saying
can i have your direct contact
It would be good if you can say here. Thank you