During this article, I will talk about Event-Sourcing implementation of your application. This layer surrounds the domain and implements the uses cases (the application-specific business rules). It orchestrates the data flow and uses the domain model and infrastructures, and has no dependency on a database, UI or special frameworks.
You may also like: Building Microservices Through Event-Driven Architecture, Part 7
For our event-sourcing system, I will take all the uncommitted events from the aggregate and call a function of the repository which will have the responsibility to save the events in the eventstore. So I will call the function AppendAsync(EventStore @event) of IEventStoreRepository.