.NET Microservices: CQRS & Event Sourcing with Kafka (Udemy.com)

the kafka and zookeeper images on docker hub used in this course are no longer active. it is no longer possible to follow this tutorial from section 2 because of this. it is also not possible to get a refund because i have watched a few minutes of the tutorial that ends up being useless early on.

I've learned a lot from this course. My only complaint is the way it is being structured. You have to go through a lot of sections, code multiple lines and files before you can even see the output. It would be better if the slice is done vertically in order to see the flow on each usecase from top to bottom like: do the add command, from controller to publish and consumed. Then proceed with another use case...

Very well conducted with advanced programming technique and SOLID principals. Would be perfect if in future can add new section to talk about how to handle new changes in existing event and entity like introducing new property into existing event or removing property.

Great introductory course to Kafka, EventSource & how they mingle together with read database & dotnet. I specifically enjoyed the simple custom cqrs mediator design. The postgres db switch at the end was a nice suprise as well. I look forward to a more advanced course with a multiple topics, saga. A conversion of a sample monolithic app to microservices would be awesome. Thanks

The Good: - I came here for the Event sourcing part which I could say it was what I expected to learn. - The instructor guides you step by step on every aspect and reply your concerns or questions. The Bad: : - there are parts that are hard to follow like using vs code to create projects, add references and nugget packages, hopefully I was able to follow along more easily using visual studio instead of vs code. Though I have learned how to use the terminal to create projects, which is nice but it kills productivity - The controllers part was bad designed, it really messes up creating a new controller for each action. there is a reason why REST was introduced with Verbs. controllers names should be nouns for resources not verbs. - The exception handling on controllers could have been implemented better with middleware to avoid duplicate code on each endpoint. Overall I can say I learned new good stuff especially event sourcing and how to replay events which was really cool.

The topic itself is difficult to understand, however watching, following and recreating project add more confidence that somthing that seems very difficult can be actually achieve. Even if some parts are still not understood, the most of the course information was asimilated.

This was one of the interesting and yet clearly focused courses I have ever taken. The author focuses on main topics and make them practical with shortest effort possible. Although there are more steps to dive deeper into each discussion, I think the core concept is more important than details. Thanks for good job. I learned a lot in a short time.

That's a great course but there are still some points that are missing. e.g What about having multiple micro services that needs to handle events from each others as they might need to update their respective read database in order to improve read performances.. I would really like to have recommendations/best practices on how to manage such behaviour.

Now this is a quality course. The instructor did a great job of explaining each and every line of code without wasting time. Now I have an in-depth understanding of CQRS, Kafka, and Event Sourcing. The last section on recreating the read DB from the Event Store blew my mind. Thanks again!

This course was good, even though I didn't like the naming of projects like 'SM-Post' or 'CQRS-ES' it was very confusing. I suggest for your future courses to use real world project names and not technical naming's. Other than that, the course was very helpful to learn CQRS and Event Sourcing.