Good explanation! It would be awesome to have an end to end example using common technologies to apply this pattern such as AXON, Kafka Streams, Cassandra, etc..
@TechPrimers3 жыл бұрын
Sure Javier. I have added it to the backlog
@hrtummala3 жыл бұрын
I see a flaw in the architecture. There is Dual write problem in matching service. The whole aim of cqrs is to eliminate distributed transactions and construct read model using events and commands.
@TechPrimers3 жыл бұрын
Thanks Hemanth. Would be happy to see the modified version so that i can share that with the audience
@DeepakPandey-ij3bz Жыл бұрын
Thanks for the tutorial. The trade api and eod trade are using same db for read and write purpose. The idea of cars defeated itself if we have this scenario bcz read and write simultaneously can choke the performance. There should be 2 separate db one for read and one fir write connected with kafka so that when write took place same data must be synchronized in read db as well
@java37113 жыл бұрын
awesome as always... good thing is you have covered the challenges also.. otherwise everything looks pretty straight forward
@pitchibovilla39983 жыл бұрын
Its awesome explanation. Can you please share implementation part also if possible
@Ravikirankada3 жыл бұрын
Nice one Ajay :-)
@SmartEngineers3 жыл бұрын
Awesome ! highly appreciable. can u plz do a video how CQRS works with Apache Kafka in practical.
@TechPrimers3 жыл бұрын
Sure bud. But will take sometime
@PavanKumar-yj8fu3 жыл бұрын
Good information, thank you!!
@mahfoozahmad79933 жыл бұрын
Very nice info, thanks a lot. Could you please create a video to implement this whole architecture. It will help us a lot.
@shyamagrawal30473 жыл бұрын
Nice one .. Thanks
@DeepakSingh-hl3er2 жыл бұрын
Thanks for such amazing explanation.
@javasystems58503 жыл бұрын
Nice explanation on CQRS and EventSource, Please can you explain what is SAGA and AXON.
@TechPrimers3 жыл бұрын
Check the SAGA video. It's already there in the channel
@indranildas79533 жыл бұрын
Very well explained. Good job. Will you be able to make a hands-on video on this case study
@TechPrimers3 жыл бұрын
Not immediately, but will do in the future
@ramanjaneyappan79643 жыл бұрын
please explain with an example implementation
@bharathsai2323 жыл бұрын
Nice video, please create a video on graph ql using aws graph ql service
@TechPrimers3 жыл бұрын
Its there in the channel Bharath. It's called AWS AppSync
@prashant123singh2 жыл бұрын
Super Awesome 👌
@soumil202 жыл бұрын
Hi. Really good video, great explanation of the different components. Do you think we should be using RDMS for the all the tables or No-SQL like Cassandra?
@shiwanichoudhary2072 Жыл бұрын
what are the other alternatives of CQRS for building microservices ?
@atech_guide3 жыл бұрын
Great video Ajay …. Could you please share the software you used to create the Architecture diagram please
@TechPrimers3 жыл бұрын
It's google slides
@sriharans41893 жыл бұрын
I guess zerodha tech website will give more details about brokerage infra and architecture.. Heaps might be best for order book..
@jwbonnett3 жыл бұрын
CQRS is eventually consistent, so wouldn't that be a problem in this case study? E.g. You modify a stock price based on how many people buy into said stock, though if that stock isn't up to date then you will have people buying more expensive or cheaper stock than the realtime price, which then affects the data integrity.
@TechPrimers3 жыл бұрын
Like i mentioned i have not considered all scenarios. The price updates gets pushed via something similar to response-processor (may be a socket connectivity) Also this is how the stock market works. Price changes every second/ms. We cannot compare it will ecommerce or other platforms where price doesn't change that frequently.
@abisheksoni33542 жыл бұрын
Good content, easy to understan , thanks
@JeffersonBienAime3 жыл бұрын
🔥🔥That is nicely done! You just solved in 18 minutes, what I was trying to accomplish in 4 four months. Keep up the good work! Subscribing now! Can you share the ppt?