In angular 1 resolving data into a route and using them in controllers was really straightforward. Below injecting orders into ordersController. $stateProvider .state('app.orders', { resolve: { .. url: "/orders/{userId}", orders: ['$stateParams', 'ordersService', function ($stateParams, ordersService) { var userId = $stateParams.userId; return ordersService.getOrders(userId); } ] } }); ordersCtrl.$inject = ['orders']; function ordersCtrl(orders) { } In angular 2 / 4 / 5 it’s quite more complicated. First, you need to create resolver:

I finished work on my presentation about “Loosely-Coupled Architecture - how to get rid of the domino effect” which will be shown as in Wrocław .NET User Group. If you are interested in this topic you can check my training offer. You can find slides from my presentation on OneDrive. Recording [PL]: Description: Traditionally, while creating our system, you don’t focus on creating our components separated from each other.

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 of how they should do it. It ended with massive collapses and posts like “The death of microservice madness”. To avoid such problems I can fully recommend Sam Newman’s book “Building Microservices”.

This post describes how to achieve database transaction, on a request level, with Autofac DI and ASP.NET WebApi. Sometimes there is a need to share transaction between two different ORMs which uses the same database - in my case Entity Framework and Dapper. It will allow you to be sure that changes, made by two different tools, will be done completely or not. To realize such scenario you can use TransactionScope class.

This post describes how to achieve database transaction, on a command level, with Autofac DI and MediatR. Sometimes there is a need to share transaction between two different ORMs which uses the same database - in my case Entity Framework and Dapper. It will allow you to be sure that changes, made by two different tools, will be done completely or not. To realize such scenario you can use TransactionScope class.

This post describes how to achieve database transaction, on a request level, with Autofac DI and ASP.NET WebApi. Sometimes there is a need to share transaction between two different ORMs which uses the same database - in my case Entity Framework and Dapper. It will allow you to be sure that changes, made by two different tools, will be done completely or not. To realize such scenario you can use TransactionScope class.

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 on Github and I encourage you to go through materials:

In cooperation with DataArt I took part in DevOps Day meetup where I presented “Cloud infrastructure management with Terraform”. You can find slides from my presentation on OneDrive. Materials Terraform documentation - https://www.terraform.io/docs/index.html Initial scripts - https://github.com/rmaziarka/terraform-azure radekmaziarka.pl repo na GitHub -https://github.com/rmaziarka/radekmaziarka.pl Provider Terraform dla Azure DevOps - https://github.com/microsoft/terraform-provider-azuredevops

This week my godfather asked me for a favor. He works in an agricultural conglomerate and is responsible for soil researchers for their clients. Currently, he found a document which covers analysis the soil, from 1995 to 2015, with an incredible amount of data. There are sheets with multiple examinations of soils every 5 years with an exact number of particular chemical elements and its absorption, as well as other parameters as saltiness, electric conductance etc.

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 of how they should do it. It ended with massive collapses and posts like “The death of microservice madness”. To avoid such problems I can fully recommend Sam Newman’s book “Building Microservices”.

Everyone loves to start a new project. Completely shiny greenfield where you can use your loved libraries and just try something new, something completely different. You are starting adding new functionalities, feature by feature, and in a glimpse of an eye half of the year have passed. Then you can feel that something is missing and during months of your work you passed over some options that currently would help you develop your app.

DevConf (former DevDay) has ended. It was a great event with interesting presentations and inspiring people who were always willing to argue on some important topics like “Why repositories are evil” ;) Even if I was slightly discouraged by machine learning’s panels (they weren’t targeted to developers) it was intriguing to check how you can use such technologies can alter life around us. I have chosen 4 presentations which I recommend from this conference:

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 on Github and I encourage you to go through materials:

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 notification You can find source codes here. Stay tuned ;)

Let’s assume that we have such read model: public class ProductReadModel { public int Id { get; private set; } public string Name { get; private set; } public int CategoryId { get; private set; } public Category Category { get; private set; } public Dictionary<int, object> FieldValues { get; private set; } } And we want store Category and FieldValues in the table, as JSON string. How to handle JSON serialization and deserialization in Dapper?

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: CREATE TABLE #Products ( Id int, Name NVarchar(128), Price decimal ) Then insert first-level entities into this table: INSERT INTO #Products SELECT P.Id, P.Name, P.Price FROM dbo.Products AS P ORDER BY P.

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 notification You can find source codes here. Stay tuned ;)

This post describes how to achieve database transaction, on a command level, with Autofac DI and MediatR. Sometimes there is a need to share transaction between two different ORMs which uses the same database - in my case Entity Framework and Dapper. It will allow you to be sure that changes, made by two different tools, will be done completely or not. To realize such scenario you can use TransactionScope class.

This post describes how to achieve database transaction, on a request level, with Autofac DI and ASP.NET WebApi. Sometimes there is a need to share transaction between two different ORMs which uses the same database - in my case Entity Framework and Dapper. It will allow you to be sure that changes, made by two different tools, will be done completely or not. To realize such scenario you can use TransactionScope class.

I finished work on my presentation about “Loosely-Coupled Architecture - how to get rid of the domino effect” which will be shown as in Wrocław .NET User Group. If you are interested in this topic you can check my training offer. You can find slides from my presentation on OneDrive. Recording [PL]: Description: Traditionally, while creating our system, you don’t focus on creating our components separated from each other.

“EAV fallacy” - assumption, that you can model complex problem with an Entity-Attribute-Value solution I’ve been involved in a few projects which tried to use the similar EAV structure (SQL or JSON replacement) to embrace difficult logic inside of the system. Mostly because we wanted to handle “unknown need” from a business perspective. For example, we wanted to use a similar structure for modeling: Apartment Restaurant Car Bike etc.

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. Recording [PL]: Materials: Articles: Weronika Łabaj - DDD Ultra-Lite Herberto Graca - Domain-Driven Design Carbon Five - Ubiquitous Language & the joy of naming Sapiens Work - DDD - The Bounded Context Explained Philip Brown - Strategies for Integrating Bounded Contexts Sebastian Gębski - The awesomeness of Modular Monolith Microsoft - Tackling Business Complexity in a Microservice with DDD and CQRS Patterns Domain Driven Design for Services Architecture Eric Evans - Domain Language Martin Fowler - Domain-Driven Design Videos:

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 on Github and I encourage you to go through materials:

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 of how they should do it. It ended with massive collapses and posts like “The death of microservice madness”. To avoid such problems I can fully recommend Sam Newman’s book “Building Microservices”.

DevConf (former DevDay) has ended. It was a great event with interesting presentations and inspiring people who were always willing to argue on some important topics like “Why repositories are evil” ;) Even if I was slightly discouraged by machine learning’s panels (they weren’t targeted to developers) it was intriguing to check how you can use such technologies can alter life around us. I have chosen 4 presentations which I recommend from this conference:

I finished work on my presentation about “Loosely-Coupled Architecture - how to get rid of the domino effect” which will be shown as in Wrocław .NET User Group. If you are interested in this topic you can check my training offer. You can find slides from my presentation on OneDrive. Recording [PL]: Description: Traditionally, while creating our system, you don’t focus on creating our components separated from each other.

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. Recording [PL]: Materials: Articles: Weronika Łabaj - DDD Ultra-Lite Herberto Graca - Domain-Driven Design Carbon Five - Ubiquitous Language & the joy of naming Sapiens Work - DDD - The Bounded Context Explained Philip Brown - Strategies for Integrating Bounded Contexts Sebastian Gębski - The awesomeness of Modular Monolith Microsoft - Tackling Business Complexity in a Microservice with DDD and CQRS Patterns Domain Driven Design for Services Architecture Eric Evans - Domain Language Martin Fowler - Domain-Driven Design Videos:

DevConf (former DevDay) has ended. It was a great event with interesting presentations and inspiring people who were always willing to argue on some important topics like “Why repositories are evil” ;) Even if I was slightly discouraged by machine learning’s panels (they weren’t targeted to developers) it was intriguing to check how you can use such technologies can alter life around us. I have chosen 4 presentations which I recommend from this conference:

“EAV fallacy” - assumption, that you can model complex problem with an Entity-Attribute-Value solution I’ve been involved in a few projects which tried to use the similar EAV structure (SQL or JSON replacement) to embrace difficult logic inside of the system. Mostly because we wanted to handle “unknown need” from a business perspective. For example, we wanted to use a similar structure for modeling: Apartment Restaurant Car Bike etc.

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. You can read this article, watch this video or read a short book about ES.

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 notification You can find source codes here. Stay tuned ;)

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 notification You can find source codes here. Stay tuned ;)

This post describes how to achieve database transaction, on a command level, with Autofac DI and MediatR. Sometimes there is a need to share transaction between two different ORMs which uses the same database - in my case Entity Framework and Dapper. It will allow you to be sure that changes, made by two different tools, will be done completely or not. To realize such scenario you can use TransactionScope class.

This post describes how to achieve database transaction, on a request level, with Autofac DI and ASP.NET WebApi. Sometimes there is a need to share transaction between two different ORMs which uses the same database - in my case Entity Framework and Dapper. It will allow you to be sure that changes, made by two different tools, will be done completely or not. To realize such scenario you can use TransactionScope class.

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 on Github and I encourage you to go through materials:

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. You can read this article, watch this video or read a short book about ES.

A few weeks ago, I began my journey to migrate an existing blog from Wordpress to Hugo. I waited for that moment for a long time, and finally, it got me. This post will be a first of in a series of many about moving to Hugo. There were several points why I decided to undertake such an activity: Wordpress is extremely slow and pages take seconds to load Even when I have cache plugins I can’t lower the load time Plugins have issues and sometimes works in contrary to each other A few months ago a backup plugin, when upgraded, made my whole page crash Making changes to the theme was very counterintuitive and timeconsuming Debugging Wordpress is extremely difficult Wordpress offered multiple options that exceed needs for a simple personal page and constrained these which were essential for me After these years I perceive Wordpress as a gateway drug – it is easy to start but maintaining this system makes a lot of pain to you.

Let’s assume that we have such read model: public class ProductReadModel { public int Id { get; private set; } public string Name { get; private set; } public int CategoryId { get; private set; } public Category Category { get; private set; } public Dictionary<int, object> FieldValues { get; private set; } } And we want store Category and FieldValues in the table, as JSON string. How to handle JSON serialization and deserialization in Dapper?

This week my godfather asked me for a favor. He works in an agricultural conglomerate and is responsible for soil researchers for their clients. Currently, he found a document which covers analysis the soil, from 1995 to 2015, with an incredible amount of data. There are sheets with multiple examinations of soils every 5 years with an exact number of particular chemical elements and its absorption, as well as other parameters as saltiness, electric conductance etc.

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 on Github and I encourage you to go through materials:

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 notification You can find source codes here. Stay tuned ;)

This post describes how to achieve database transaction, on a command level, with Autofac DI and MediatR. Sometimes there is a need to share transaction between two different ORMs which uses the same database - in my case Entity Framework and Dapper. It will allow you to be sure that changes, made by two different tools, will be done completely or not. To realize such scenario you can use TransactionScope class.

I finished work on my presentation about “Loosely-Coupled Architecture - how to get rid of the domino effect” which will be shown as in Wrocław .NET User Group. If you are interested in this topic you can check my training offer. You can find slides from my presentation on OneDrive. Recording [PL]: Description: Traditionally, while creating our system, you don’t focus on creating our components separated from each other.

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. Recording [PL]: Materials: Articles: Weronika Łabaj - DDD Ultra-Lite Herberto Graca - Domain-Driven Design Carbon Five - Ubiquitous Language & the joy of naming Sapiens Work - DDD - The Bounded Context Explained Philip Brown - Strategies for Integrating Bounded Contexts Sebastian Gębski - The awesomeness of Modular Monolith Microsoft - Tackling Business Complexity in a Microservice with DDD and CQRS Patterns Domain Driven Design for Services Architecture Eric Evans - Domain Language Martin Fowler - Domain-Driven Design Videos:

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 of how they should do it. It ended with massive collapses and posts like “The death of microservice madness”. To avoid such problems I can fully recommend Sam Newman’s book “Building Microservices”.

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 of how they should do it. It ended with massive collapses and posts like “The death of microservice madness”. To avoid such problems I can fully recommend Sam Newman’s book “Building Microservices”.

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 of how they should do it. It ended with massive collapses and posts like “The death of microservice madness”. To avoid such problems I can fully recommend Sam Newman’s book “Building Microservices”.

Let’s assume that we have such read model: public class ProductReadModel { public int Id { get; private set; } public string Name { get; private set; } public int CategoryId { get; private set; } public Category Category { get; private set; } public Dictionary<int, object> FieldValues { get; private set; } } And we want store Category and FieldValues in the table, as JSON string. How to handle JSON serialization and deserialization in Dapper?

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: CREATE TABLE #Products ( Id int, Name NVarchar(128), Price decimal ) Then insert first-level entities into this table: INSERT INTO #Products SELECT P.Id, P.Name, P.Price FROM dbo.Products AS P ORDER BY P.

Let’s assume that we have such read model: public class ProductReadModel { public int Id { get; private set; } public string Name { get; private set; } public int CategoryId { get; private set; } public Category Category { get; private set; } public Dictionary<int, object> FieldValues { get; private set; } } And we want store Category and FieldValues in the table, as JSON string. How to handle JSON serialization and deserialization in Dapper?

Everyone loves to start a new project. Completely shiny greenfield where you can use your loved libraries and just try something new, something completely different. You are starting adding new functionalities, feature by feature, and in a glimpse of an eye half of the year have passed. Then you can feel that something is missing and during months of your work you passed over some options that currently would help you develop your app.

Everyone loves to start a new project. Completely shiny greenfield where you can use your loved libraries and just try something new, something completely different. You are starting adding new functionalities, feature by feature, and in a glimpse of an eye half of the year have passed. Then you can feel that something is missing and during months of your work you passed over some options that currently would help you develop your app.

Everyone loves to start a new project. Completely shiny greenfield where you can use your loved libraries and just try something new, something completely different. You are starting adding new functionalities, feature by feature, and in a glimpse of an eye half of the year have passed. Then you can feel that something is missing and during months of your work you passed over some options that currently would help you develop your app.

More than two years ago I started my journey with public speakings. And it went better than I expected. I want to share my feelings why is worth to start your own public speaking journey in your company / community group / work team. In term of public speaking I am not talking only about standing on the stand and shouting towards people but all activities like: giving a presentation or lightning talk in your project / company being a trainer during a workshop present your ideas in meeting in front of your superiors / managers sharing your knowledge in podcast / youtube videos Therefore, all these events when you are heard by a group of people and they only listen to you.

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 of how they should do it. It ended with massive collapses and posts like “The death of microservice madness”. To avoid such problems I can fully recommend Sam Newman’s book “Building Microservices”.

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 of how they should do it. It ended with massive collapses and posts like “The death of microservice madness”. To avoid such problems I can fully recommend Sam Newman’s book “Building Microservices”.

More than two years ago I started my journey with public speakings. And it went better than I expected. I want to share my feelings why is worth to start your own public speaking journey in your company / community group / work team. In term of public speaking I am not talking only about standing on the stand and shouting towards people but all activities like: giving a presentation or lightning talk in your project / company being a trainer during a workshop present your ideas in meeting in front of your superiors / managers sharing your knowledge in podcast / youtube videos Therefore, all these events when you are heard by a group of people and they only listen to you.

DevConf (former DevDay) has ended. It was a great event with interesting presentations and inspiring people who were always willing to argue on some important topics like “Why repositories are evil” ;) Even if I was slightly discouraged by machine learning’s panels (they weren’t targeted to developers) it was intriguing to check how you can use such technologies can alter life around us. I have chosen 4 presentations which I recommend from this conference:

In cooperation with DataArt I took part in DevOps Day meetup where I presented “Cloud infrastructure management with Terraform”. You can find slides from my presentation on OneDrive. Materials Terraform documentation - https://www.terraform.io/docs/index.html Initial scripts - https://github.com/rmaziarka/terraform-azure radekmaziarka.pl repo na GitHub -https://github.com/rmaziarka/radekmaziarka.pl Provider Terraform dla Azure DevOps - https://github.com/microsoft/terraform-provider-azuredevops

This post describes how to achieve database transaction, on a request level, with Autofac DI and ASP.NET WebApi. Sometimes there is a need to share transaction between two different ORMs which uses the same database - in my case Entity Framework and Dapper. It will allow you to be sure that changes, made by two different tools, will be done completely or not. To realize such scenario you can use TransactionScope class.

A few weeks ago, I began my journey to migrate an existing blog from Wordpress to Hugo. I waited for that moment for a long time, and finally, it got me. This post will be a first of in a series of many about moving to Hugo. There were several points why I decided to undertake such an activity: Wordpress is extremely slow and pages take seconds to load Even when I have cache plugins I can’t lower the load time Plugins have issues and sometimes works in contrary to each other A few months ago a backup plugin, when upgraded, made my whole page crash Making changes to the theme was very counterintuitive and timeconsuming Debugging Wordpress is extremely difficult Wordpress offered multiple options that exceed needs for a simple personal page and constrained these which were essential for me After these years I perceive Wordpress as a gateway drug – it is easy to start but maintaining this system makes a lot of pain to you.