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.
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 of encapsulation.
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.
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.
Akka.NET simple example with Github Api Posted on by Michal Franc In this post I want to a simple introduction to Akka.NET using an example app based on Github api. I have been diving into Akka .NET lately. My first encounter with this technology was on Vaughn Vernon workshop in Krakow. The main event had couple of side presentation and one of them was about Akka project in Java world. It was a magic to me. Couple years later, I accidentally found ( probably on twitter ) Bartosz Sypytkowski blog and ...
Akka.NET is a .NET port of famous actor model programming framework Akka, well known for the JVM community. This blog post discuss how in few lines of code we can distribute our computations by deploying actors on the remote machines. And all of that using F# functional API.
macko (32 816,53)
http://pawlos.blo... (31 603,45)
pzielinski (27 178,29)
gordon_shumway (21 178,87)
paduda (20 336,33)
psz750 (13 018,14)
rroszczyk (10 383,88)
Damian (9 041,08)
danielplawgo (7 235,99)
arek (6 807,94)
burczu (6 214,22)
PaSkol (5 393,84)
lukaszgasior (4 097,38)
jj09 (3 578,06)
jedmac (3 318,39)
http://jakub-flor... (3 224,66)
CaMeL (2 954,87)
spetz (2 798,25)
mnikolajuk (2 596,93)
lkurzyniec (2 590,69)