Microservices Reference

Each engine service should have a dedicated page describing:

• responsibility and boundary
• inbound authentication
• outbound authentication
• runtime/deploy configuration
• operational checks

Service Pages

• Gateway
• Orchestrator
• Scheduler
• Storage
• Identity
• Transformers
• Dashboard
• Egress HTTP
• Egress FTP
• Egress SSH/SFTP
• Egress IMAP
• Egress SMTP
• Egress RabbitMQ
• Egress Google Workspace
• Egress Positionstack
• Egress Weatherstack
• Egress Joke API

Capability providers (registry-driven, no orchestrator coupling): see Deploy integration contract.