Most important super easy and practical explanation coupled with again easy diagrams and finally keeping entire subject short. Keep up the good work ffriend.
Hi Ashok, nice explaination. Can you explain more about data base transaction and rollback. And what if we don't use message queue in orchestration or command base saga
Can you develop a Spring Boot for Orchestration example. Saga started from 9.40. payment is done is stock is not available? There must be procurement service then.
Is SAGA works on http request / response done accross microservices. I mean; Do u mean by firing a event is nothing but sending a http post request from Mic1 to Mic2, and if in case it fails it will throw 403 error, and if success then 200/201 response will be sent..
💡 Welcome to Ashok IT..!! 💡
👉 Register Here For Online Training : bit.ly/3Crpgbr
🔥 Download Android App : bit.ly/3Z2vXcO
🔥 Download IOS App (MyInstitute) : apple.co/3IcEao3
👉 ORG Code For IOS : CNFXJ
🌐 Visit Our Website : ashokitech.com/
Very useful and clear explanation Ashok. Thanks.
Most important super easy and practical explanation coupled with again easy diagrams and finally keeping entire subject short. Keep up the good work ffriend.
good explanation, thank you
excellent efforts sir.. very good explanation
Hi Ashok, Thanks for the beautiful explanation. Is their a practical implementation video on on Saga Orchestration?
The tagline seems similar to Butte University's - start here..go anywhere👍
Hi Ashok, nice explaination. Can you explain more about data base transaction and rollback. And what if we don't use message queue in orchestration or command base saga
Awesome explained
Glad you liked it
Do SAGA pattern make locking at database level . Say , 5 inventory is available and 10 user parallely order same inventory ?
Can you develop a Spring Boot for Orchestration example. Saga started from 9.40. payment is done is stock is not available? There must be procurement service then.
Is SAGA works on http request / response done accross microservices. I mean; Do u mean by firing a event is nothing but sending a http post request from Mic1 to Mic2, and if in case it fails it will throw 403 error, and if success then 200/201 response will be sent..
It's tightly coupled. But, the youtuber taking about loosely coupled.