marcduiker

My definition of serverless

My definition of serverless is that:

• You don't have full responsibility of the infrastructure, which is a good thing.
• Your resources should scale up and down automatically, based on the load.
• You only pay for what you actually use, so the consumption model.

Usages

• Glue code, connect services

marcduiker

Serverless Days Amsterdam Conference Script

This document contains the script for the online ServerlessDays Amsterdam Conferene. We're using a combination of OBS, Skype & NDI Tools to combine our streams. Streaming is done to Restream.io which in turn forwards it to YouTube, Twitch and Periscope.

Roles

The lines in the script are prefixed with the role of the person who needs to undertake an action.

• TECH = The person who's controlling OBS

marcduiker

Hi ServerlessDays speaker!

Here are the instructions for joining our conference on May 8th. Please read them through carefully so the experience on the conference day will be as smooth as possible. Another email will follow, which contains the exact time you need to be online during the conference.

There are three actions we ask you to do now:

1. Read this entire message, yes, all of it!
2. Send us your prerecorded session before Friday if you haven't done so already.
3. Connect with our co-organizer, Marc Duiker, on Skype: m.duiker_1

Tech requirements

marcduiker

Serverless Days Meetup Script for Online Events

This document contains the script for the online ServerlessDays Amsterdam Meetup. We're using a combination of OBS, Skype & NDI Tools to combine our streams. Streaming is done to Restream.io which in turn forwards it to YouTube, Twitch and Periscope.

Roles

The lines in the script are prefixed with the role of the person who needs to undertake an action.

• TECH = The person who's controlling OBS

marcduiker

‎Event Storming‎​

Q: What is it?

A: A workshop format to collaboratively explore a domain.

Different types

There are three types of event storming

marcduiker

Lab 0 - Prerequisites

Goal

During this workshop we're going to write Azure Functions in C# (.NET Core). The goal of this lab is to very that the required SDKs, IDE and tooling are installed.

Steps

1. SDKs

marcduiker

Building a resilient workflow using Durable Functions

XASA Workshop

Congratulations! Today is your first job as a software engineer at XASA, the Xpirit Aeronautics and Space Administration. You are responsible for creating a system which reacts to detected Near-Earth Objects (NEOs).

A satellite is continuously scanning the skies for these NEOs. The satellite transmits its findings to ground stations which in turn send the data to Azure.

It's your job to ensure the incoming data is analyzed to assess the risk of impact, stored, and to notify the required organizations of this risk and possible counter-measures (think Armageddon style).

marcduiker

using System.Collections.Generic;
using System.Collections.Immutable;
using System.Linq;
using System.Reflection;
using Microsoft.Azure.WebJobs;

// ReSharper disable once CheckNamespace
namespace DurableFunctions.Demo.DotNetCore.Reflection
{
    public class FunctionNameExtractor

marcduiker

requests  | 
project timestamp, id, operation_Id, operation_Name, duration, cloud_RoleName, cloud_RoleInstance  | 
where cloud_RoleName =~ 'FUNCTION_APP_NAME' | 
join kind= inner (dependencies | project target, duration, performanceBucket, operation_Id) on operation_Id |
order by duration desc | 
take 100

marcduiker

requests | project timestamp, id, operation_Id, operation_Name, success, resultCode, duration, cloud_RoleName  | join kind=inner (exceptions | project operation_Id, message, outerMessage, innermostMessage) on operation_Id | where cloud_RoleName =~ '<FUNCTION_APP_NAME>' and operation_Name == '<FUNCTION_NAME>' | order by timestamp desc | take 100