Serverless App Stack

Objective

The point of this repo is to productionise a common application pattern.

Through creating the "best" use of Bicep Modules, an archetype has been created that can easily be leveraged by other similar applications.

Quickstart

RG="serverlessApim"
az group create -g $RG -l westeurope
az deployment group create -g $RG -u https://raw.githubusercontent.com/Gordonby/AzureBicepServerlessAppStack/main/bicep/application/icecreamratings.json

View of the bicep modules

The layers

The modules have been structured in 3 layers

Foundational
Archetype
Application

Foundational

Foundational bicep modules are opinionated in the configuration that best suits your enterprise. They are not simple modules that expose every possible value for every resource type. Foundational modules are precise, and often deploy more than one resource where they need to be tightly bound (bundles).

Archetype

Archetypes fulfils a use case without being application specific. They integrate disparate Azure services that should be leveraged together to create a new module that is simple to deploy and easy for your application teams to leverage.

Application

These modules are totally specific to your application or enterprise function. They decide names, they provide source code, they configure empty infrastructure to something meaningful.

Benefits and Risks of this approach

Benefits

Speed. Identifying common application patterns, and being able to onboard teams to a standardised infrastructure setup is a big plus.

Standardisation.

Risks

Teams that fork the archetype without genericising for other teams.

Overfitting to specific application use cases

The main components

APIM -> FunctionApp -> CosmosDb

Diagram view of all components

Gordonby/AzureBicepServerlessAppStack

ErrorLooks like something went wrong!

About

Topics

Resources

Uh oh!

Stars

Watchers

Forks

Uh oh!

Languages

Error
Looks like something went wrong!