Companies Home Search Profile

Build an Event Store in C# .NET for CQRS and Event Sourcing

Focused View

7:19:37

0 View
  • 1 -Introduction.mp4
    01:37
  • 2 -Course Structure.mp4
    04:43
  • 3 - Source Code in C#.html
  • 1 -What is Event Sourcing.mp4
    16:43
  • 2 -The Business Insights of Event-Sourced Systems.mp4
    04:09
  • 3 -The Technical Advantages of Event-Sourced Systems.mp4
    06:18
  • 4 -Building your own Event Store vs. using a third party solution.mp4
    06:53
  • 1 -What is CQRS.mp4
    09:17
  • 2 -Implementing a Command.mp4
    21:59
  • 3 -Implementing Command Handlers.mp4
    25:48
  • 4 -Queries.mp4
    06:50
  • 1 -Implementing Aggregate Roots.mp4
    39:07
  • 1 -High-Level Architecture.mp4
    09:32
  • 2 -What database should you use.mp4
    08:12
  • 3 -Using AWS DynamoDB as an Event Store.mp4
    05:45
  • 1 -Overview of the components we will build.mp4
    04:36
  • 2 -Data flow within the architecture and how the event store will operate.mp4
    05:22
  • 3 -Implementing DynamoDB Tables by Hand.mp4
    14:24
  • 4 -Implementing DynamoDB Tables with CloudFomration.mp4
    13:42
  • 5 -Creating a DynamoDB Event Store in C# and .NET Core.mp4
    52:33
  • 6 -How to manage concurrency violations.mp4
    22:59
  • 7 -Memory Event Store.mp4
    08:24
  • 1 -What is a Snapshot.mp4
    07:39
  • 2 -Implementing a Snapshot.mp4
    17:37
  • 1 -What is a Projection.mp4
    10:01
  • 2 -Implementing a Projection.mp4
    07:32
  • 1 -Publishing and consuming domain events.mp4
    10:32
  • 2 -Implementing a consistent domain event publication process.mp4
    41:57
  • 1 -The importance of read models.mp4
    07:03
  • 2 -Implementing a read model in C# using MySQL on AWS.mp4
    44:13
  • 1 -Final Thoughts.mp4
    04:10
  • Description


    Build an Event Store in C#. NET for Event-Driven Architectures using CQRS, Event Sourcing and Domain-Driven Design

    What You'll Learn?


    • Understand the importance of using business (domain) events as a source of truth in your solution.
    • Understand how to use and implement the ubiquitous language in your source code.
    • Understand how to build an event store, how it functions, and how to use it properly.
    • Understand how to separate a system between read and write functions to optimize flow and performance by using CQRS.
    • Understand how to use Domain-Driven Design (DDD) in your solution using aggregate roots.
    • Understand what projections are and how to program projections.
    • Understand how to publish domain events and failure events.
    • Understand what snapshots are and how to use them properly.
    • Understand what read-models are and how to implement them.

    Who is this for?


  • Developers and Architects who are curious about event-driven architectures by utilizing CQRS, Event Sourcing, and Domain-Driven Design (DDD).
  • What You Need to Know?


  • It is not entirely required but it would be helpful to know how to program in C#. If you are a Java developer, you can easily convert the concepts or even the source code to Java.
  • More details


    Description

    Real-time communication and feedback to your customers are more important then ever. Customers have become used to immediate feedback on the actions they take in your software. It is very hard in create, read, update, and delete (CRUD) based applications to provide this sort of responsiveness that your customers are demanding. Event-based solutions that are based on CQRS, Event Sourcing, and Domain-Driven Design (DDD) can offer deep insides in real-time to your customers and to your business. More importantly, you won't loose data in an event-sourced solution when compared to CRUD-based solutions because your solution will be able to provide the context on why changes happened and record changes into an immutable log, the event store.

    In this course, you will learn about the importance of using domain events as your source of truth instead of pieces of data that are incomplete in CRUD-based applications. You will be able to tell stories on what happened when and why. You will be able to answer future questions by your customers and business even though you may not have all the requirements at hand when you design and build your event-sourced solution.

    At the very heart of your solution will be the event store. The event store is the source of truth in your entire solution. We will be building an event store in C#. NET and utilizing AWS DynamoDB as the persistence mechanism. However, the provided C# source code can easily be converted to Java or other languages. For the actual persistence, you could also use MySQL, PostgreSQL, MongoDB, and others. The C# code is abstracted so that can you can re-use it for specific persistence implementations. The concepts and code can work for on-premise, cloud only, or hybrid models. For an example read model implementation, we will be creating a read model using MySQL in AWS.

    Once you understand the power of event sourcing, you won't go back.

    Who this course is for:

    • Developers and Architects who are curious about event-driven architectures by utilizing CQRS, Event Sourcing, and Domain-Driven Design (DDD).

    User Reviews
    Rating
    0
    0
    0
    0
    0
    average 0
    Total votes0
    Focused display
    Category

    C#

    Students take courses primarily to improve job-related skills.Some courses generate credit toward technical certification. Udemy has made a special effort to attract corporate trainers seeking to create coursework for employees of their company.
    • language english
    • Training sessions 30
    • duration 7:19:37
    • Release Date 2025/02/24