Event Sourcing & CQRS | Stock Exchange Microservices Architecture | System Design Primer

Тәжірибелік нұсқаулар және стиль

This video covers the usage of Event Sourcing & CQRS using Stock Exchange Server Architecture example
📌 Related Videos
===============
🔗 Caching Architectures - • Caching Architectures ...
🔗 Strangler Application Pattern - • Strangler Application ...
🔗 Rapids Rivers and Ponds - • Rapids Rivers Ponds | ...
📌 Related Playlist
================
🔗Spring Boot Primer - • Spring Boot Primer
🔗Spring Cloud Primer - • Spring Cloud Primer
🔗Spring Microservices Primer - • Spring Microservices P...
🔗Spring JPA Primer - • Spring JPA Primer
🔗Java 8 Streams - • Java 8 Streams
🔗Spring Security Primer - • Spring Security Primer
💥 Join TechPrimers Slack Community: bit.ly/JoinTechPrimers
💥 Telegram: t.me/TechPrimers
💥 TechPrimer HindSight (Blog): / techprimers
💥 Website: techprimers.com
💥 Slack Community: techprimers.slack.com
💥 Twitter: / techprimers
💥 Facebook: TechPrimers
💥 GitHub: github.com/TechPrimers or techprimers.github.io/
🎬Video Editing: FCP
---------------------------------------------------------------
🔥 Disclaimer/Policy:
The content/views/opinions posted here are solely mine and the code samples created by me are open sourced.
You are free to use the code samples in Github after forking and you can modify it for your own use.
All the videos posted here are copyrighted. You cannot re-distribute videos on this channel in other channels or platforms.
#CQRS #SystemDesignPrimer #EventSourcing

Пікірлер: 35

  • @javisartdesign
    @javisartdesign3 жыл бұрын

    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..

  • @TechPrimers

    @TechPrimers

    3 жыл бұрын

    Sure Javier. I have added it to the backlog

  • @java3711
    @java37113 жыл бұрын

    awesome as always... good thing is you have covered the challenges also.. otherwise everything looks pretty straight forward

  • @PavanKumar-yj8fu
    @PavanKumar-yj8fu3 жыл бұрын

    Good information, thank you!!

  • @DeepakSingh-hl3er
    @DeepakSingh-hl3er2 жыл бұрын

    Thanks for such amazing explanation.

  • @prashant123singh
    @prashant123singh2 жыл бұрын

    Super Awesome 👌

  • @pitchibovilla3998
    @pitchibovilla39983 жыл бұрын

    Its awesome explanation. Can you please share implementation part also if possible

  • @shyamagrawal3047
    @shyamagrawal30473 жыл бұрын

    Nice one .. Thanks

  • @soumil20
    @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?

  • @DeepakPandey-ij3bz
    @DeepakPandey-ij3bz11 ай бұрын

    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

  • @hrtummala
    @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.

  • @TechPrimers

    @TechPrimers

    3 жыл бұрын

    Thanks Hemanth. Would be happy to see the modified version so that i can share that with the audience

  • @Ravikirankada
    @Ravikirankada3 жыл бұрын

    Nice one Ajay :-)

  • @JeffersonBienAime
    @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?

  • @SmartEngineers
    @SmartEngineers3 жыл бұрын

    Awesome ! highly appreciable. can u plz do a video how CQRS works with Apache Kafka in practical.

  • @TechPrimers

    @TechPrimers

    3 жыл бұрын

    Sure bud. But will take sometime

  • @indranildas7953
    @indranildas79533 жыл бұрын

    Very well explained. Good job. Will you be able to make a hands-on video on this case study

  • @TechPrimers

    @TechPrimers

    3 жыл бұрын

    Not immediately, but will do in the future

  • @javasystems5850
    @javasystems58503 жыл бұрын

    Nice explanation on CQRS and EventSource, Please can you explain what is SAGA and AXON.

  • @TechPrimers

    @TechPrimers

    3 жыл бұрын

    Check the SAGA video. It's already there in the channel

  • @mahfoozahmad7993
    @mahfoozahmad79933 жыл бұрын

    Very nice info, thanks a lot. Could you please create a video to implement this whole architecture. It will help us a lot.

  • @abisheksoni3354
    @abisheksoni33542 жыл бұрын

    Good content, easy to understan , thanks

  • @bharathsai232
    @bharathsai2323 жыл бұрын

    Nice video, please create a video on graph ql using aws graph ql service

  • @TechPrimers

    @TechPrimers

    3 жыл бұрын

    Its there in the channel Bharath. It's called AWS AppSync

  • @atech_guide
    @atech_guide3 жыл бұрын

    Great video Ajay …. Could you please share the software you used to create the Architecture diagram please

  • @TechPrimers

    @TechPrimers

    3 жыл бұрын

    It's google slides

  • @sriharans4189
    @sriharans41893 жыл бұрын

    I guess zerodha tech website will give more details about brokerage infra and architecture.. Heaps might be best for order book..

  • @shiwanichoudhary2072
    @shiwanichoudhary207210 ай бұрын

    what are the other alternatives of CQRS for building microservices ?

  • @ramanjaneyappan7964
    @ramanjaneyappan79643 жыл бұрын

    please explain with an example implementation

  • @jwbonnett
    @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.

  • @TechPrimers

    @TechPrimers

    3 жыл бұрын

    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.

  • @shivamgupta5476
    @shivamgupta54763 жыл бұрын

    Make a video on it

  • @FWTteam
    @FWTteam2 жыл бұрын

    Is it a ppt?

  • @TechPrimers

    @TechPrimers

    2 жыл бұрын

    Google slides

  • @FWTteam

    @FWTteam

    2 жыл бұрын

    Can you share the slide please?

Келесі