Concurrecy. Are you an optimist?

Conquering concurrency one at a time

In this short article I will not be touching any asynchronous code or concepts. It will also be not about eventual consistency.

There are specific situations when we may have problems with the other type of concurrency, and the biggest problem is discovering the possibility that the system allows for data to be overwritten without end user’s intentions.
The solution is easy.

Read more Concurrecy. Are you an optimist?

On design: A short story of an unique date

(and how we broke the Gmail)

A simple assumption. An action is performed at a given time, so it can be a unique value used for sorting by date. Right?

Gmail developers thought that way, and it seems they were not entirely correct.

On one of the cold nights of the Autumn 2016…

Read more On design: A short story of an unique date

Art of system integration

System integration reviewed

The system integration tips presented here are to achieve data integrity, performance, quality, cooperation, and finally fewer support issues.

Tips are based on an integration with web service communication and data transfer between at least two parties.

If you prefer bullet-point version of best practices, scroll down this page.

Read more Art of system integration

Web services in .NET – big picture

Web services

In this technical article, I will present the full picture of web services, basing on WCF technology over HTTP using IIS when going into details. Both beginners and experienced developers may use this article as a checklist of things they already know or want to learn.

By the full picture I mean from a need to have a web service, choosing web service type, correct configuration (e.g. security), deployment environment, to testing tools. I assume you have already created your “Hello web service” application, or just want to have a closer look at the topic.

Read more Web services in .NET – big picture

On design: E-mail is unreliable

E-mail is unreliable

Having worked on various projects where e-mails were used I came to this exact conclusion. E-mail is unreliable, as a medium.
It is not obvious while coding it happily, but certainly gets painful after doing maintenance over an application for a prolonged period of time.

“I’ve sent an e-mail and now it’s not my problem” attitude, assumption that an external component always works, will bring trouble to the final product.

Let’s look at using e-mail in the app-wide, business-wide perspective.

Read more On design: E-mail is unreliable