Q&A - EventStoreDB, Event Sourcing, CQRS, and DDD

Webinars
,

This webinar has ended

Register to watch the recording on-demand

Register now


Event Sourcing adoption is rising and so is the number of questions about applying the pattern, along with CQRS and Domain-Driven Design. We already addressed some of the basics in our previous webinars, and now we’re hosting an open Q&A session where you get a chance to ask about what is unclear for you. We don’t expect to get through answering every question, so make sure that you submit your questions upfront and we’ll address the most common and important ones.

At the end of the session, we will answer questions from the audience (if we get enough time left). Reserve your seat now!

You can register and submit your question/s using the form below.

Webinar overview

Title: Q&A - EventStoreDB, Event Sourcing, CQRS, and DDD

Date/Time: 13 August 2020, 16:00 (UTC)

Duration: 1 hour

Host: Mat McLoughlin and Alexey Zimarev

Description: A chance for you to ask questions about EventStoreDB, Event Sourcing, CQRS and DDD. With Mat McLoughlin (Head of Product) and Alexey Zimarev (Developer Advocate) from Event Store.

Register for the webinar


Related posts

Webinar: Q&A - Inside EventStoreDB

Webinars
,

Have you ever wanted to know more about how EventStoreDB works or what goes on "under the hood"? Here's your chance for you to ask questions about the technical side of EventStoreDB server and database technology. With James Geall (VP of Engineering) and Mat McLoughlin (Head of Product) from Event Store.



Webinar: Event Sourcing and CQRS

Webinars
,

We are going a little beyond the very basics of Event Sourcing and will start implementing an application that uses the CQRS pattern. During the webinar, Alexey will introduce the CQRS concept and will demonstrate why CQRS is important in event-sourced systems. There will be a great deal of live coding again, demonstrating all the moving parts of both command and query sides in a real-life, although simplistic, application with a domain model.