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 and keep it. So let’s talk about persisting it.

Exactly one year ago I’ve published first post on this blog. It was simple “Hello world” that were followed by some posts related to 2016 edition of Get Noticed contest and after that by some more or less technical related stuff. Since it’s first anniversary of this first, lame “Hello world” post I can’t just write simple “Hi there” again. And because I’m taking a little breath before 2017 edition of said contest I don’t want to write any hard, technical stuff. So let me tell you about some things that I...

I’m building my Get Noticed project from the scratch. And since 3 months is actually a very short span of time, I need compromise between doing some things fast (boring ones) and doing other things in a way that will allow me to write about it and not be ashamed to show some code afterwards. That means I’ll need to incur a technical debt in few areas of project. And I must watch it closely to not allow it to grow without control or interests will probably kill me.

Actor model concept fascinated me since I’ve heard about it for the first time. It’s been on my todo list ever since and Get Noticed 2017 is great opportunity to give it a try. That’s why there is an actor responsible for almost anything in Me2.0. But, what is an actor, actor model and are benefits of using it in our projects? You’ll find out in a minute.

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.

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 things works magic with memory) and maybe someone will have any use for that. Let’s start with simple things – dynamic data masking.

Welcome to the fifteenth episode of my course “Becoming a software developer” in which we will implement password encryption, authorization and authentication using JWT.

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.

Tworzenie puli obiektów to częsta praktyka stosowana w bibliotekach serializujących. We wpisie sprawdzam, czy używanie takiego podejścia dla małego bloku pamięci jest efektywne i czy nie lepiej użyć niskopoziomowego słowa kluczowego stackalloc.

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.