This repository contains a basic “Azure Serverless Application” as a basis for the implementation of additional functionality. The purpose of this is education.
For documentation of Azure services, architecture patterns and other theory material consider Microsoft sites. A recommandation: Serverless apps: Architecture, patterns, and Azure implementation. Microsoft Learn platform contains plenty of high-quality tutorials which are very much recommended. Specifically there is a Learning Path “Create serverless applications”.
Providing customers with a solution based on Azure Services at a professional level, requires competencies of: Development, provisioning and operational management. These 3 pillars are equally important and relevant in all phases of an implementation project. This lab contains challenges for those pillars which are inspired by real world situations and requirements of GARAIO AG projects.
You need to have your own Azure subscription to work with this lab. As a GARAIO employee you have these two possibilities for a subscription with sufficient budget:
By default, the MSDN-based subscription is tied to the organisation tenant. You can transfer it to a private directory to not pollute the organisations AD with e.g. App Registrations: Manual.
To setup the prepared application you need an Azure DevOps account/organisation with the same user account that you use for the Azure Portal with your Subscription.
You can easily create a new account or add a private organisation if you use your work account. Start here: https://azure.microsoft.com/en-us/services/devops/
Sign in to Azure DevOps
with your company account (or if you already have an account)Start free
if you don’t yet have a loginAll code artefacts regarding the basic “Azure Serverless Application” you find in the folder Foundation
. You can (but don’t have to) build your realisations of the challenges based on this. It includes a completely automated deployment of all Azure resources (as explained in the “Preparation” document of each track).
Extend the basic application with additional functionality. Also includes challenges for the frontend application (JavaScript based).
Extend the existing “Infrastructure as Code” artefactes and implement a CI/CD strategy.
Provide possibilities to visualize operational key aspects of the application. Enable business insights as well as the detection and notification of technical problems and possible optimizations.
To simplify the selection of challenges depending on your interests here some recommendations:
Feel free to share your work. Please follow these guidelines.