Containerized Node.js Demo App for Azure App Service.
| Status | Pipeline | Website URL | CDN Endpoint |
|---|---|---|---|
| dev.yaml | nodejs-demo-dev.onazure.io | nodejsdemo-dev.azureedge.net | |
| production.yaml | nodejs-demo.onazure.io | nodejsdemo-prod.azureedge.net |
This demo leverages the Static Content Pattern in Cloud Architecture.
The images and CSS can be served from app itself or pulled from external host, e.g. CDN via ASSETS_BASE_URL environment variable.
In real life you have more than one environment.
-
Azure Pipelines Best Practices
- CI pipeline for feature branches and
main - Deploy when pushing to
mainorproductionbranches - See ./azure-pipelines for working pipelines and details
- CI pipeline for feature branches and
-
Asset Pipeline
The included cd.yaml pipeline shows how to upload assets to Blob Storage and purge the Azure CDN cache as part of your deployment process. -
CI/CD & Versioning
Example versioning and promotion strategies leveraging git commit messages, git tags andpackage.json.
-
Azure PaaS
This app is hosted on Web App for Containers -
Azure App Insights integration
Using appinsights npm package and Express.js middleware with just a few lines of code. See monitor.js
| Method | Path | Description |
|---|---|---|
| GET | / |
root |
| GET | /health |
health check endpoint |
| POST | /webhooks/test |
accepts JSON and logs output |
This is an example healthcheck endpoint with standardized JSON per draft IETF standard
{
"status": "pass",
"version": "0.7.1",
"details": {
"uptime": {
"component_type": "system",
"observed_value": 24208698,
"human_readable": "0 days, 6 hours, 43 minutes, 28 seconds",
"observed_unit": "ms",
"status": "pass",
"time": "2021-04-12T11:45:32.508Z"
},
"env": {
"WEBSITE_HOSTNAME": "azure-nodejs-demo-dev.azurewebsites.net",
"WEBSITE_INSTANCE_ID": "03e7481d3d5ff1e67e297f158abd943ce8c8b920fa55dc7bf0565e86886404a8",
"ASSETS_BASE_URL": "https://nodejsdemo-dev.azureedge.net"
}
}
}