-
Design the architecture for a SaaS web application which is deployed to Azure.
-
React Web App
-
.NET API
-
Node JS Cron Job
-
Database
-
Design and highlight Logging and Monitoring solution to be implemented.
-
Create a YAML file to represent the pipeline to deploy both the React App and the .NET API.
- The infrastructure is deployed and is not managed by these pipelines
- I am in GitHub and am part of an organization. There are different repos listed below here.
- some-app-infra
- some-app-tf
- some-app-react
- some-app-node
- some-app-dot-net
- github-actions
- github-workflows
- Can I deploy containers directly to Azure? Yes, using Azure Container Instances.
- Can I deploy containers that run on a schedule?
- Can I build a .NET container with Docker?
- What database should I use?
- Should I show the multi-tenant structure?
- Should I do a multi-resource-group structure? No, this is a single application made of multiple services, so it should be held together.
- Lifecycle environments - Depending on needs, you could achieve this with resource groups, subscriptions, management groups, or tenants. However, this is probably more effort than what is needed to show the skills in this example. As a note, I would look at having three environments; DEV, STAGE, and PROD. I would also include an OPS environment which would host things like the DNS, Monitoring, and Container Registry, so there is one location where all of that lives and the environments can remain relatively sanitary.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent