What is a real life project - one can ask. The real life - in terms of software development - is built of limitations. Your time is limited, the budget is limited, your abilities are limited and even knowledge of what you should exactly do is limited. Only your client's expectations and need to maintain the legacy code are unlimited. Funny - but let's puts jokes aside as this article should have some limit too.
In my experience, SignalR has proven to be a great way to push events from server to the clients, both web-based, as well as mobile apps. In this post I would like to describe how SignalR handles scaling out to multiple hosts. I will also try to resolve a problem that occurs, when you are trying to do that with OWIN self-hosted SignalR.
Application Insights is a great Azure based service for developers, similar to New Relic, that allows you to monitor an application, analyze its performance and get a deeper look into errors that occur in production. All of that without having to care about the infrastructure and management of the monitoring tools. Here, I'll describe how to deal with correlating all telemetry data gathered within one request to an OWIN based application.
Recently, working on the Parkanizer project our team faced the problem of backing up MongoDB located within Docker container. As we are .NET guys we are using Azure as our cloud infrastructure provider. We are storing our backups in the Azure Blob storage. This time we wanted to do the same with the Mongo backups.