Azure – The ultimative Service Guide

Microsoft is delivers day by day new, improved and updated services in the Microsoft Azure Cloud. For new customers and even for experienced Azure engineers it’s sometimes hard to find the right service for a problem. It’s possible to solve the same problem with different services and often it depends on the expected customer base.

Over the years the Microsoft Azure Poster team developed a very useful view on the Azure infrastructure which helps to understand better when to use which service.

Microsoft Azure Infographic 2015 2.4_UNSEC 2017-07-25 07-34-07.png

This cool and helpful poster should be available in every team working with the Microsoft Azure Cloud. It’s available for free here.

In addition I had a helping hand during the last weeks and months from Ricardo Niepel , an evangelist for Microsoft Azure. He is also the author of the new interactive Azure Platform overview here. This makes the decision which service to use much easier and it helps everybody to not loose track when Microsoft delivers new services regularly.

Hey node developers, switch to .NET Core – now!

Several years ago I started building a bigger project as a Software as a Service application. Beside all the different technical requirements, being able to work directly on my MacBook Pro without starting virtual machines, was a big wish. At this time a tool chain based on Node.js, Express, NPM and WebStorm was available. Over the years building backend services with Node.js, and this means with JavaScript, felt like rapid prototyping. Getting started is very fast and lightweight but when the project grows compile time features like a strong type system are missing. Year over year I did reviews how to get esp. the beauty of C# and the powerful compiler infrastructure of .NET back.

intelligentservice

In the last month Microsoft released Visual Studio for Mac and with it the investments into .NET Core increased. Building backend services in Visual Studio for Mac based on .NET Core and ASP.NET Core including the out of the box support in Azure App Services is definitely what I was looking for.

Because of that I decided to give it a spin. After a couple weeks working with the framework I can say it was the right decision because of the following key reasons:

  • Full managed and type safe environment based on the powerful C# compiler
  • Broad ecosystem for components similar to NPM via NuGet
  • Ability to convert runtime errors in compile time errors 
  • Hosting the results on Linux, Docker Containers or just Azure App Services
  • ASP.NET Core comes with out of the box easy to use Dependency Injection system
  • ASP.NET Core learned and steeled the best things from the node + express chain
  • C# Attribute and Extension-Classes are unbeatable to beatify your code 

And last but not least everything works well on my MacBook Pro without the need of a single virtual machines – Thanks Microsoft for letting me keep the platform I love!