Skip to main content

FAAS: Serverless architectures with Function as a Service

After PAAS(Platform as a Service), IAAS(Infrastructure as a Service) and SAAS(Software as a Service), it is now time for FAAS; Function as a Service.  FAAS is one of the incarnations of Serverless architectures(BAAS, BackEnd as a Service is another one).

Let’s have a look at what Microsoft has to offer in the FAAS space; Azure Functions.

Azure Functions is a serverless event driven experience that extends the existing Azure App Service platform. These nano-services can scale based on demand and you pay only for the resources you consume.

Getting started

  • Go to the Azure Functions product page. Click on the big green Get started button.

image 

  • Log in with an account linked to an Azure subscription.
  • If you logged in succesfully, you’ll be redirected to a Get started page(an Angular 2 app Smile) where you can configure the following information
    • Your subscription: select one of the associated subscriptions for this account
    • Name: select a name for your Azure Function(should be unique)
    • Region: select a target region
  • Click on the Create + get started button.

image

  • After the Azure function is created, you will be redirected to the Azure portal where you are welcomed by a Quickstart screen.

image

  • Let’s walk through the  Quickstart.
    • First we choose one of the sample scenario’s; let’s pick the Timer scenario.

image

    • Second choose a programming language. At the moment C# and JavaScript are supported.

image

    • Click on the Create this function button to complete the Quickstart.
  • And there we have it, our first Azure function:

image

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more