Behind the Scenes - CQRS & Event Sourcing Architecture

In this meetup we’ll explore the importance of naming and its impact on our code. Then, we'll explore the principles principles of event sourcing, while highlighting the importance of naming, and the impact it has on our code. We’ll discuss how to model your data and implement business logic using this pattern and how to improve your system through the segregation of reads and writes with specialized read models. We’ll also discuss CQRS, a key part of an architecture based on event sourcing and provide you with real life examples. Please note the lectures will be given in Hebrew (the slides will be in English).

Schedule:

18:00- 18:30 - Drinks and food

18:30 - 19:20 - Name in Vain: Improving Design One Word at a Time

19:20 - 19:30 - Break

19:30 - 20:15 - Developing Event-Driven Microservices with Event Sourcing and CQRS

20:15 - More drinks!

Name in Vain: Improving Design One Word at a Time - Boris Litvinsky

As developers, we all appreciate readable code. Yet, we tend to neglect the one thing that makes it so - naming. This negligence however, tends to impact our code in far greater capacity than we realize. In fact, it threatens the one thing we care about the most - software design. In this talk we’ll rediscover the importance of naming, explore the anatomy of bad name and see what makes a good one.

Bio

Boris is a software developer since age 16, having experience in mobile development, backend systems and for the past 4 years – client side development. During his career, Boris got a chance to work in companies of various sizes – from garage-stage startup to a colossal corporate environments. He has immense passion for well-written, highly maintainable, well tested code. Boris believes that products internal code quality has a direct impact on software’s external quality – the business value the product gives the management and the product owner.

Developing Event-Driven Microservices with Event Sourcing and CQRS - Lidan Hifi

Most systems today store only the current state of their business entities. However, we can look at the current state through a different lens- as a derivative of previous behaviors, and store those behaviors as a sequence of events instead of the current state of the entity. The current state will be derived by replaying the events. Event sourcing is a great way to implement event-driven applications, and it’s often combined with CQRS (Command Query Responsibility Segregation) which is a key part of an architecture based on event sourcing. In this talk I will cover the principles of event sourcing pattern, how to model your data and implement business logic using this pattern and how to improve your system through the segregation of reads and writes with specialized read models. You will also learn how those concepts fit in with event-driven micro services through a real life example- an invoices management app we built at Wix.

Bio

Lidan is a fullstack developer at Wix, works both on the server-side and the client-side.

He has 10 years of experience in writing code in a variety of technologies and he also consults various companies.

In the past two years, Lidan is a part of the Wix CRM platform team, and is focused on building awesome communication products for customers and businesses.