Hi there. It’s been a while. Sadly I’ve acquired a rather nasty writer’s block. I’ve been doing some talks and other activities in the meantime. I’m pretty much unlocked at the moment and I’ll resume my writing really, really soon. However, I’m after a long thinking and planning session. Starting January 2019 I’m going to… Read More »
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+ (compatibility level 130+). What’s really great about that approach is that unless you need to retrieve state from the certain point in time or browse through… Read More »
My last blog post was about a feature in SQL Server called Row Level Security Policy. It’s quite simple and known feature for people who’re working directly with databases. But most .NET developers are using ORM of some kind to work with DB, and some of them tend to be blind to stuff that is not… Read More »
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… Read More »
When I’ve started working with Azure SQL there were some differences to SQL Server that I’ve needed to get used to. One of the first was that you just can’t query other databases that you’re already in, querying for [OtherDB].[dbo].[SomeTable] just wasn’t possible anymore. It appears that it may not be possible, but you actually… Read More »
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… Read More »
Storing data in multitenant environments always required some consideration. With Cosmos DB we have 2 options that are really worthy of our attention so let’s weight some pros and cons.
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.
On Saturday week and a half, I’ve been on finals gala of Get Noticed contest. Unlike last year I won’t write a summary about the event itself. Instead, I’ll share one really simple thing with you. On gala, I’ve been rewarded with special prizes by two sponsoring companies – Microsoft and Objectivity. Awards were really neat… Read More »
For the last 3 months I’ve been participating in Get Noticed contest, just like a year ago. I’ve persevered to end of the contest just like almost 200 people out of almost 1000 that started it. In the last week we as contestants was supposed to vote for other projects to choose 25 finalists from… Read More »
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.
Working with Azure means you can use on of databases it provides in PaaS model. If you use them you don’t have to install and configure i.e. SQL Server on some kind of (virtual or not) machine. Databases in PaaS model have a lot of other virtues but let’s not go there in this post,… Read More »
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.
While I can’t say casting is a way to go in C#, it’s a rather common operation. It’s good to know there is more than one way of doing that and the best way depends on current circumstances.
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.
As I’ve mentioned in previous posts about Akka.NET, everything that actor knows is stored in memory. While we can skip any database or IO related bottlenecks because things in memory are generally speaking very fast, we must remember that memory is not a place where you can store your data for an extended period of time… Read More »
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… Read More »
Microsoft Flow is a service I’ve been working with for some time and poking it to discover some of its possibilities. Basically, it’s service that allows to create and manage workflows from ready to use blocks representing triggers and actions.
How many times have you stored something in key/value collection? Most probably it was Dictionary or some kind of implementation of IEnumerable<KeyValuePair<TKey, TValue>>. 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,… Read More »
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… Read More »