Microservices Reference¶
Each engine service should have a dedicated page describing:
- responsibility and boundary
- inbound authentication
- outbound authentication
- runtime/deploy configuration
- operational checks
Terminology¶
A capability provider is an HTTP service that registers with the capability-registry. Workflows use exclusively type: service_call plus capability_name and path for integrations, transforms, and scripts. Built-in control/context steps remain orchestrator-owned. Do not add new first-class integration types.
Service Pages¶
Platform¶
- Gateway
- Orchestrator
- Capability Registry
- Scheduler
- Storage
- Identity
- Dashboard
- Script Execution Service (SES)
- Variables
- Transformers
Capability providers (egress / connectors)¶
- Egress HTTP
- Egress FTP
- Egress SSH/SFTP
- Egress IMAP
- Egress SMTP
- Egress RabbitMQ
- Egress Google Workspace
- Egress Positionstack
- Egress Weatherstack
- Egress Joke API
- Example Echo (C#)
- Example Echo (Go)
- Egress S3
- Egress PostgreSQL
- Egress Azure Service Bus
Happy path: Integration end-to-end.
Registry-driven deploy checklist: Deploy integration contract.
Canonical provider contract: Contract 17.