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.