Dlaczego Bounded Contexty są ważne – podsumowanie

W tym poście będę zbierał materiały opublikowane w cyklu “Dlaczego Bounded Contexty są ważne”: Wprowadzenie Szkielet implementacji Przykład braku kontekstów – Partie produktów a działy firmy Przykład braku kontekstów – Parametry produktów Przykład braku kontekstów – Produkty pojedyńcze i produkty grupowe Architektura zdarzeniowa

Event Storming – retrospection

Event Storming is a workshop which makes it easier to understand business domain and to translate it into an architecture of the application. It was first described by Alberto Brandolini in his blog post, in November 2013. I won’t elaborate on what it is and how to conduct this workshop – there are plenty of materials on the Internet…. Continue reading

Domain Driven Design – Strategic design & Microservices

I finished work on my presentation about “Domain Driven Design – Strategic Design & Microservices” which will be shown as in Silesian Microsoft Group. If you attended this presentation please share your thoughts in this survey. You can find slides from my presentation on Slideshare, or download it from OneDrive. Articles: Weronika Łabaj – DDD Ultra-Lite Herberto Graca… Continue reading

CQRS in 4 steps – presentation

I finished work on my presentation about “CQRS in 4 steps” which will be shown during 4Developers conference. You can find slides from my presentation on Slideshare. Also, you can check my blog posts: splitting code to commands and queries introducing different data access creating simple read model creating read model asynchronously with SignalR notification Moreover, there are sources… Continue reading

“Building Microservices” by Sam Newman – book review

TD DR: Mandatory book for every developer who wants to work with microservices. Microservices architecture is a trend in a modern software, which is currently implemented across our whole IT industry. Unfortunately, people started applying microservices without any greater understanding how they should do it. It ended with massive collapses and posts like “The death of microservice madness”. To avoid such problems… Continue reading

Dapper – JSON type custom mapper

Let’s assume that we have such read model:

And we want store Category and FieldValues in the table, as JSON string.  How to handle JSON serialization and deserialization in Dapper? TypeHandlers TypeHandlers are an option in Dapper to serialize / deserialize objects during saving and querying the database. First, we define an implementation of ITypeHandler interface:

SetValue method… Continue reading

Dapper – many to many relation in a single request

During my CQRS journey, I implemented many-to-many data querying, in the single database request. I achieved getting all products with associated entities at the same time. To achieve the same, we need to define a temporary table to store all first-level entities:

Then insert first-level entities into this table:

With such temporary table, we are able… Continue reading

CQRS – Third step – Simple read model

This post series is driven by my lightning talk about how to introduce CQRS to your project. I thought that would be good to explain this topic further for people who won’t be attending my presentation. I will write about: splitting code to commands and queries introducing different data access creating simple read model creating read model asynchronously with SignalR… Continue reading