Once you understand how Event Sourcing works, the most common thought is: "What happens when you have a lot of Events? Won't it be inefficient to fetch every event from the EventStore and replay all of them to get to current state?". It might be. But to combat this, you can leverage snapshots to give you a representation of your aggregates state at a point in time. You can then use this as a checkpoint and them only replay the events since the snapshot. 🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw 💥 Join this channel to get access to source code & demos! null 🔥 Don't have the JOIN button? Support me on Patreon! https://www.patreon.com/codeopinion 📝 Blog: https://codeopinion.com/ 👋 Twitter: https://twitter.com/codeopinion ✨ LinkedIn: https://www.linkedin.com/in/dcomartin/ 0:00 Intro 2:24 Snapshots 5:19 Code Implementation 5:39 Aggregate 7:05 Repository 9:31 Creating a Snapshot 10:18 Demo #eventsourcing #cqrs #softwarearchitecture