Event Sourcing: Events Evolution, Versioning, and Migration
· โ˜• 12 min read
Systems do evolve and unavoidably evolution leads to breaking changes... If you are doing event sourcing, events evolution is unavoidable, ultimately you will crash ๐Ÿ”ฅ๐Ÿš’ into it. The more you know, the better you prepared, as they say ๐Ÿค“

React Json Schema Form
· โ˜• 11 min read
Just want to share one of the tools I'm using daily. A React component for building Web forms from JSON Schema. Transform annoying, time consuming task into simple routine

Different Flavours of Events
· โ˜• 15 min read
Events, events, events... Events are everywhere... Event Sourcing, Event Streaming, Asynchronous services and much more. All these technical contexts have something in common, but a lot is different. And this is what this article is about ๐Ÿค“

Are Controllers Real Evil?
· โ˜• 11 min read
Too often, I found myself with bloated Controllers. Or when Controllers seemed like an awkward and redundant solution. Anyhow I kept using them. I know I'm not the only one who trapped in a similar situation? Is it Controllers or us doing something wrong? Here I tried to shed a bit of light on this topic.

Post articles through CI/CD pipeline. Or having a Tech Blog in 2020.
· โ˜• 12 min read
I wrote this article in the Visual Studio Code. It was a markdown file in the separate article-dedicated GitHub branch, which eventually became a Pull Request. And if you are reading it, it means that the post made its way to the master branch. The merge event triggered the process that transformed markdown file into a static HTML file, which was finally pushed to a hosting. And now you can read it.

Server-side Redux. Part III. The Code.
· โ˜• 13 min read
The State Management Goes Wild his is the final article of the series where we explore Redux and its boundaries. In the previous articles, weย first dived into the main principles of the Redux, then weย tried to move things aroundย and conceptually move Redux from one side to another. This article is all about hands-on experience, and by the end of it, we will have a working application that will follow the design we settled before.

Server-side Redux. Part II. The Design.
· โ˜• 7 min read
The State Management Goes Wild This is the second article of the series where we will try to find out if thereโ€™s a place for Redux on the other side of the fence. Even though this series is base on the assumption that you are more or less familiar with what is Redux, donโ€™t worry if not, as we covered all necessary concepts in the previous article. Take your time and make yourself comfortable with Redux.

Server-side Redux. Part I. The Redux.
· โ˜• 7 min read
The State Management Goes Wild This is the first article of the series where we will try to find out if there’s a place for Redux on the other side of the fence. Even though this series is base on the assumption that you are more or less familiar with the Redux, but don’t worry if not, as we will go over necessary concepts first. Once we are confident with the Redux as a React state manager, we will be exploring how we can use it as a back-end state management and state distribution tool and gradually build the conceptual design.

CQRS: Querying via HTTP
· โ˜• 8 min read
This article continues the series dedicated to the CQRS pattern. We will be looking at the Command Query Responsibility Segregation pattern as an architecture, particularly dive into the Querying part and try to find out how to fit it in the HTTP. At the time this article is written, two main protocol versions exist HTTP/1.1 and HTTP/2. Version 3.0 is in the draft, so we are not considering it. The main difference between 1.

CQRS: Commanding via HTTP
· โ˜• 9 min read
This article starts the series dedicated to CQRS on top of HTTP. We will be looking at the Command Query Responsibility Segregation pattern as an architecture, particularly dive into the Commanding part and try to find out how to fit it in the HTTP. At the time this article is written, two main protocol versions exist HTTP/1.1 and HTTP/2. Version 3.0 is in the draft, so we are not taking it into consideration.

Web Browser Anatomy
· โ˜• 8 min read
Web Browser is a big and sophisticated application, built from multiple components. It obligated to satisfy different boring standards, to facilitate developers with stable contracts. You might know these contracts as HTML, CSS, and JavaScript. Any valid code or markup will be recognized and processed by one of the browser modules. The browser glues together all its modules with the Browser Object Model (BOM) API, akaย Web API. This is something that empowers JavaScript to operate on HTML and CSS.

Single Page Application. React example.
· โ˜• 7 min read
It is not a guide for building a single page application with the help of React JS. This article is about the tool that empowers modern web to look the way it looks today and provide a seamless experience of navigation, enabling single page applications to exist. Good old days Back in the days, the internet and everything around it was different, as well as expectations from web sites. A typical web site would be a set of HTML pages tied together with cross-references.

CQRS: Intro
· โ˜• 7 min read
Command Query Responsibility Segregation This pattern gains popularity lately. And thereโ€™re certain benefits of using it as well as drawbacks. I would like to share my own experiences and thoughts on this topic. โ„น๏ธ Don’t forget to check out more advanced series dedicated to appliying CQRS architectural patter on top of HTTP [CQRS via HTTP]. The series covers in depth main actors of the pattern, such as Commanding and Querying, as well as how do they fit in the HTTP.