Note: There are a ton of individual resources, even down to the webhook level in Azure. The easiest place to start is probably the resource groups themselves, but Big Things are included here.
For a more thorough list and discussion of our cloud resources, see the infrastructure overview.
| Resource | dev | prod | description |
|---|---|---|---|
| Search Service | Link | Link | Used to index curations by facet |
| Redis | Link | Link | Used by most other applications to share data at the service instance level |
| Resource | dev | prod | prod-eu | description |
|---|---|---|---|---|
| App Service | Link | Link | Link | The "metal" hosting the application. Deployed to from Azure DevOps. |
| Container Registry | Link | Link | Used to store the UI container |
| Resource | dev | prod | prod-eu | description |
|---|---|---|---|---|
| Application Insights | Link | Link | Contains all telemetry for the service instance | |
| App Service | Link | Link | Link | The "metal" hosting the application. Deployed to from Azure DevOps. |
| Container Registry | Link | Link | Used to store the service container | |
| CosmosDB | Link | Link | Used to store the curations and package definitions | |
| Azure Storage Queue | Link | Link | The service is waiting for messages from the Curations queue to process those curations and stored in CosmosDB |
| Resource | dev | prod | description |
|---|---|---|---|
| Application Insights | Link | Link | Contains all telemetry for the crawlers |
| Blob storage | Link | Link | This is where is stored the crawler's results. |
| App Service | Link | The "metal" hosting the application. Deployed to from Azure DevOps. | |
| Azure Storage Queue | Link | Link | This is used to store the tasks for the crawlers. There are several queues related with the crawlers: cdcrawlerprod-inmediate, cdcrawlerprod-soon, cdcrawlerprod-normal, cdcrawlerprod-later. The one that is actively used is cdcrawlerprod-normal, the rest of them are keep for historical reason, when the ghcrawler was used, those queues are going to be removed in the future. |
| Resource | Dev | Prod | Description |
|---|---|---|---|
| KeyVault (shared across everything) | Link | Used to store secrets used by operations to access resources external to Azure. | |
| @clearlydefinedoutlook Azure Active Directory (must sign in with @clearlydefined) | Link | The identity provider that controls access to the Azure subscription. Not used for actual email. | |
| Clearly defined superuser | Link | The user that has god mode on Azure Portal, can be used to elevate access for other users or to perform operations requiring subscription admin. | |
| Traffic Manager | Service UI | Used for geofencing and load balancing. There are one for the Service and another one for the UI | |
| Logic Apps | Link | Link | The logics Apps are used to store the curations made in github into the curations queue of Azure Storage Queue for further processing and storage |
| Data Factory | Link | Used to backup the definitions and the harvest data |