Azure Storage Account is one of the foundation services of Azure. Pretty much all other services use it under the cover in a way or another. This service is simple, works great, and has crazy SLA and redundancy capabilities. However, it doesn't provide a point in time restore. Meaning that if you corrupt or delete some data, there's no way to recover it. There are some solutions that you can find over the internet, but unfortunately, none of them is a silver bullet. Let's explore and compare som
In my career, more than half of the bugs I encountered were related in a way or another to a null value being propagated where it shouldn't have been—therefore resulting in unexpected behaviors or a nasty NullReferenceException. The problem Why is null such a problem in C#? Well... the null problem (a.k.a the billion-dollar mistake) breaks many assumptions you can make about the programming language. In more theoretical terms, it breaks the Liskov substitution principle. (One of the famous SOL
Service Fabric is a great framework, but yet a complicated one. Often, when we try to improve the security of the cluster, we end up adding a lot of complexity in our development pipeline. The local development experience become a nightmare and there's a big lost in productivity for team. But! It doesn't have to be that way. Productivity and security could play well together if you think about them from the start. Let's take a look at how we can improve our cluster security following all the in
Moving to the cloud is pretty exciting. When you open the door to your dev teams it can go crazy fast and next thing you know you have a big mess of Azure resources all over the place. Putting in place a good set of governance guidelines will help you keep everything under control. The first thing to think about is your Azure Subscriptions structure. This is the very first step that will drive many of your following decisions in order to achieve a good Azure governance. Goals 1. Security 2.
Azure Application Gateway is a pretty neat and cheap service offered by Azure. It’s a level 7 load balancer which means it understand HTTP and can route traffic according to a specific URL pattern. In my opinion it’s a must have in a micro service world these days. Here’s why: The problem If you are like us, you probably have an infrastructure with one hostname per micro service finance.contoso.com user.contoso.com sales.contoso.com This seems fine at first, but it comes with some issues 1
Application logging is the kind of software problem that has been solved so many times, in so many ways. It makes it really hard to choose THE right framework to use when starting a new project. Sometimes it almost feel like coding your own framework will be a good idea (Please don’t do that). The first thing you should ask yourself is what are your requirements. Try to think about what will the development, testing, and debugging experience be like. How will you search through your logs to find