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 »
As you’ve probably seen in previous posts about Akka.NET, actor model is no rocket science and is really easy and fun to start with. However entire actor model may seem like closed and hermetic ecosystem, today I’ll show you how to poke actors in way that’ll make them poke back.
Entity Framework (and other ORMs) are in general great pieces of software that makes developers lives so much easier by letting us thinking about objects when we’re working with data persisted in some underlying database. This makes development much easier than writing raw SQL queries. But some of us tend to get too comfy and… Read More »
First of three months in Get Noticed contest just passed. Some code were written, and some posts have been too. Let’s wrap this month up quickly and see what I’ve got for the foreseeable future.
One of the concepts of actor model that could be hard to grasp at the begining is fact that we will not operate on direct reference to actor instance. This can be a bit confusing before you’ll get used to it but by not using any direct references you’re sure to achieve very good level… Read More »
Yesterday I’ve writen about dynamic data masking in Azure SQL (works with SQL Server 2016 too). It is very interesting and simple feature. But can we use it with our beloved Entity Framework?
Along with Get Noticed contest I’m a bit preoccupied with other activities. One of them is preparing to take 70-473 Exam (cloud and data related stuff). Since I’m reading and using cert related stuff I could as well write about it – I’ll probably remember everything I’ll write about for rest of my life (writing about… Read More »
Let’s take a closer look at our actors, how their life looks like, what exactly they’ve been doing and what they can do. As they are basic building block of applications built on actor model it’s crucial to understand and being able to communicate with them.
In previous post I’ve explained briefly what actor model is and why it’s so fun. Today we’ll create our ActorSystem instance, learn what it is and send first messages to them. I hope it will be nice and easy start.