Getting Started
Architecture
Service Platform
NServiceBus
Transports
Persistence
ServiceInsight
ServicePulse
ServiceControl
Monitoring
Shape the future
Samples

MassTransit Connector Docker Deployment

Component: ServiceControl

Overview

When MassTransit is used with the rest of the platform, there are in total 4 containers that get deployed:

  1. particular/servicecontrol
  2. particular/servicecontrol-ravendb
  3. particular/servicecontrol-masstransit-connector
  4. particular/servicepulse

The particular/servicecontrol and particular/servicecontrol-ravendb containers are used to ingest messages from the error queue. The particular/servicecontrol-masstransit-connector container reads messages from the MassTransit system's error queues and moves them into the error queue to be ingested by ServiceControl. The particular/servicepulse container exposes a web interface to allow users to retry failed messages back to the MassTransit system.

Docker Compose

name: particular-platform-masstransit-recoverability
x-transport: &transport-env
  environment:
    RAVENDB_CONNECTIONSTRING: "http://servicecontrol-db:8080"
    ALLOWMESSAGEEDITING: true
    SHOW_PENDING_RETRY: true
    
     #[RabbitMQ]
    TRANSPORTTYPE: "RabbitMQ.QuorumConventionalRouting"
    CONNECTIONSTRING: "host=host.docker.internal"
    MANAGEMENTAPI: "http://guest:guest@host.docker.internal:15672"

    #[AzureServiceBus]
    #TRANSPORTTYPE: "NetStandardAzureServiceBus"
    #CONNECTIONSTRING: "<connection-string>"

    #[Amazon SQS]
    #TRANSPORTTYPE: "AmazonSQS"
    #AWS_REGION: "<region>"
    #AWS_ACCESS_KEY_ID: "<access-key>"
    #AWS_SECRET_ACCESS_KEY: "<secret-access-key>"
    #CONNECTIONSTRING: "Region=$AWS_REGION;AccessKeyId=$AWS_ACCESS_KEY_ID;SecretAccessKey=$AWS_SECRET_ACCESS_KEY"

services:
  service-control-db:
    container_name: servicecontrol-db
    image: particular/servicecontrol-ravendb:6
    volumes:
      - sc-data:/var/lib/ravendb/data
  service-control:
    depends_on:
      service-control-db:
        condition: service_healthy
    container_name: servicecontrol
    image: particular/servicecontrol:6
    command: "--setup-and-run"
    ports:
      - 33333:33333
    << : [*transport-env]
  masstransit-connector:
    container_name: masstransit-connector
    image: particular/servicecontrol-connector-masstransit:latest
    command: "--setup-and-run"
    << : [*transport-env]
  service-pulse:
    depends_on:
      - service-control
    container_name: servicepulse
    image: particular/servicepulse:latest
    ports:
        - 9090:9090
    environment:
        - SERVICECONTROL_URL=http://localhost:33333/api/
        - ENABLE_REVERSE_PROXY=false
        - SHOW_PENDING_RETRY=true
        - ALLOW_MESSAGE_EDITING=true

volumes:
  sc-data:
Feedback