MACH (micro service based, API first, cloud native, headless)

- 1 minutes read - 105 words

Just an architecture style MACH got me attention. It is short for micro service based, API first, cloud native, headless. There are two of projects I involved one are in this architecture style. One is sitecore based, another one is developed. Kubernetes, nodejs, npm, strapi tsoa are used. Their mapping is as following.

  • micro services based: multiple services based on expressjs

  • api first: tsao

  • cloud native: more advanced than cloud native, kubernate native is used.

  • headless: strapi

Here I have a diagram for the developed one.

Kubernetes ClusterFront End[Namespace]Back End[Namespace]Utiliy Services[Namespace] Kubernetes API API Gateway     DevOpsClient AppsHelm Charts AzureActive Directory ACR Cosmos DB AzureKey Vault LoadBalancer Externaldata stores CI/CDAzure PipelinesAUTHhelm upgrade RBAC[ASYNC]HTTP[ASYNC]HTTP[ASYNC]    Pod Identity docker pushdocker pullKubernetes Plant-UML
comments powered by Disqus