We have many solutions for versioning data through time. One of the cleanest, most transparent and pretty effortless in my opinion are Temporal Tables which are available in MS SQL 2016+. What’s really great about that approach is that unless you need to retrieve state from the certain point in time or browse through changes in a specified time range, you can query against a versioned table in an exactly same way that you would do with any other one.

In some scenarios, like single-database multi-tenant or soft delete ones, you could want to restrict access to your rows based on a value stored in one or more values stored in your columns in example IsDeleted flag or some kind of TenantId column. Since SQL Server 2016 we have a wonderful tool for that called Row Level Security Policy.

I’m working with Azure for quite a while now. Almost every single one of my projects lands there eventually and even if I don’t deploy it there, I’m using one of it’s databases. Recently I’ve started using Visual Studio Team Services for storing code and managing my every pet or demo project that I want to keep private for now. But there is one service available on Azure that I’m using for a very long time with great success and I really like to have it in my project – it’s Application Insights combined ...

A while ago I wrote about creating Actor System and top-level actors. Sadly it was stored in a static field. And keyword static is … let’s say it’s not one of my favourites. Today I’ll show you how I’m doing the exact same thing but in Dependency Injection container.

When I’m writing this there are still 2 and a half hour to the end of “Get Noticed 2017 contest. Let’s wrap everything up. The basic goal was to develop open source project and blog about this at least 2 times a week. I did a post about my project when I’ve released first alpha/beta version of it, you can read it here.

Since the beginning of march, I’m working on a pet project called Me 2.0 as a part of Get Noticed contest. Now I’m ready(ish) to release it’s the first version to the public, along with its companion app. TL;DR: Links for the app and messenger bot are at the end of this blog post.

In the previous post, I’ve briefly described part of a process of persisting state of our actor. I’ve told you about storing events and I’ve mentioned things called snapshots. This post is entirely about them.

In one of my posts about Akka.NET I’ve covered actor selections and paths. Sadly I’ve skipped one rather important part regarding allowed characters for actor paths and what to do if our name cannot be used for creating an actor. And recently I’ve received a question about why I’m creating actors using encoded string. This is the cause.

How many times have you stored something in key/value collection? Most probably it was Dictionary or some kind of implementation of IEnumerable>. More than a few times I wanted to store more than one value under single key, most common solution for this situation is Dictionary with collection of some kind as value type, but do you remember about type that was designed just for that and is seen much less often in code?

Lately I’ve seen some posts about authentication made easy and simple with various packages and how it’s great we doesn’t haven’t to store logins and passwords in our databases anymore due to global availability of social identity providers. It’s true that making simple authentication with of of those providers is simple today. And in Azure App Services it’s even simpler, it really can be done in 5 minutes.