I love the video. Very insightful. However I notice you make the same mistake I see other channels make with these types of videos. The cons of both designs are not really cons in morden implementations. Take CRUD for example. The history for most CRUD apps that need some history tracking is tracked either by creating a table for History or using changelog if they want an audit history. For event sourcing you mention things like performance overhead and event versioning without any reason why this is a CON. Not trying to be annoying here but these sort of things lead to interns and junior devs telling me they don't want to build with system design "A" because it is too slow but don't know why it is slow.
Thanks so much for the feedback and for watching! You're absolutely right-modern CRUD apps handle history well with techniques like changelogs or history tables. The intent in discussing it as a con was to highlight that while CRUD can support history tracking, it requires additional effort that isn't native to the design-whereas with event sourcing, tracking is inherent in the model. It's not a hard con. Similarly, with event sourcing, the points about performance and versioning were meant as things to consider, not dealbreakers. Since this is an intro video, we had to keep it brief and couldn’t dive into every nuance. It's always a fine balance on UA-cam-too much and people get bored. But I appreciate your input-we'll be sure to add more context in future content to avoid misunderstandings. Thanks again for engaging!
Level up your system design skills at: systlemdesignschool.io/
Very high quality videos. Hope this channel grows
Awesome video. I recommend linking the website you mentioned in the video description.
oh great idea, just added!
I'm experimenting CDC (eg: DynamoDB Streams). A good way to combine Event Source and CRUD.
Nice! CDC is a great way to bridge the two
thanks
I love the video. Very insightful. However I notice you make the same mistake I see other channels make with these types of videos. The cons of both designs are not really cons in morden implementations. Take CRUD for example. The history for most CRUD apps that need some history tracking is tracked either by creating a table for History or using changelog if they want an audit history. For event sourcing you mention things like performance overhead and event versioning without any reason why this is a CON. Not trying to be annoying here but these sort of things lead to interns and junior devs telling me they don't want to build with system design "A" because it is too slow but don't know why it is slow.
Thanks so much for the feedback and for watching! You're absolutely right-modern CRUD apps handle history well with techniques like changelogs or history tables. The intent in discussing it as a con was to highlight that while CRUD can support history tracking, it requires additional effort that isn't native to the design-whereas with event sourcing, tracking is inherent in the model. It's not a hard con. Similarly, with event sourcing, the points about performance and versioning were meant as things to consider, not dealbreakers.
Since this is an intro video, we had to keep it brief and couldn’t dive into every nuance. It's always a fine balance on UA-cam-too much and people get bored. But I appreciate your input-we'll be sure to add more context in future content to avoid misunderstandings. Thanks again for engaging!
@@SystemDesignSchool When do we get the deep dive. I want to recommend your videos to my interns. I like the presentation style. Simple.