The Particular Service Platform can be deployed using Linux containers instead of Windows hosting. This page gives an overview of how the pieces fit together and links to the detailed deployment guide for each one. It's the starting point for anyone setting up the platform in containers for the first time; each linked page has the full configuration reference for that piece.
Component overview
Only the Error and Audit instances need a RavenDB container; Monitoring instances don't store any data. Audit and Monitoring instances are optional but recommended.
Deploying the pieces
Deploy the pieces in this order:
- RavenDB, one container per Error or Audit instance. See Managing ServiceControl RavenDB instances via Containers.
- ServiceControl Error instance, the only required piece. Enable integrated ServicePulse on this container so no separate ServicePulse container is needed. See Deploying ServiceControl Error instances using Containers.
- ServiceControl Audit instance (optional), if audit message history is needed. See Deploying ServiceControl Audit instances using containers.
- ServiceControl Monitoring instance (optional), if endpoint performance monitoring is needed. See Deploying ServiceControl Monitoring instances using containers.
A standalone ServicePulse container is still available, and is needed to view a Monitoring instance and an Error instance from a single address, or to manage more than one Error instance from the same ServicePulse. See Running ServicePulse in containers for that scenario.
Next steps
For examples of Particular Service Platform containers used together, including Docker Compose and Kubernetes using a Helm chart, see the Platform Container Examples repository.
- Migrating an existing Windows-hosted installation to containers: Migrate ServiceControl to container deployment.
- Deploying alongside MassTransit: Deploying the MassTransit Connector.