+1 to your tech karma if you're reading this

Back in the days, when I didn't have a cluster of Raspberry Pi computers, running Kubernetes using said cluster seemed like a good idea, at least for the purpose of learning things. Now, in hindsight, it's pretty clear that it's not all peachy-rosy for those who run k8s on Raspberry Pi nodes.

My first attempt at learning Kubernetes was about a year ago. I've managed to setup a minikube  instance and run a cluster of RabbitMQ + monitoring stack on top ( Prometheus and Grafana ). While this all worked well inside a single minikube instance, doing such lab activities without being able to project my meager experience onto real-life project did not provide for a great learning opportunity.

 Recently I had overhauled build and deployment procedure for one of my pet projects. Project is a web app built with ASP.NET MVC and Web API, and it's hosted on one of the shared hosting platforms. Those unfortunate enough to still use shared hosting know, that there's little alternative to deploy there besides using FTP file-share.

In my previous post I was talking about how to create dynamic proxy using Castle DynamicProxy . Now, I want to shed some light on how to make sure that your proxy class complies with your interface, using special unit-tests.

The subject of this post is not really new I guess, but since I myself stumbled upon such puzzle, I decided to blog about my own experience.

As you maybe realized from the title, I will talk about Akka.NET , a .NET port of famous Akka framework, combined with MEF  dependency injection library, and how you can use mocks (I will use Moq to leverage mocking power) to unit-test Akka.Net actors.