3.0 KiB
Bindings
Using bindings, you can trigger your app with events coming in from external systems, or invoke external systems. Bindings allow for on-demand, event-driven compute scenarios, and dapr bindings help developers with the following:
- Remove the complexities of connecting to, and polling from, messaging systems such as queues, message buses etc
- Focus on business logic and not the implementation details of how interact with a system.
- Keep the code free from SDKs or libraries
- Handles retries and failure recovery
- Switch between bindings at runtime time
- Enable portable applications where environment-specific bindings are set-up and no code changes are required
Bindings are developed independently of Dapr runtime. You can view and contribute to the bindings here.
Supported Bindings and Specs
Every binding has its own unique set of properties. Click the name link to see the component YAML for each binding.
| Name | Input Binding | Output Binding | Status |
|---|---|---|---|
| Kafka | V | V | Experimental |
| RabbitMQ | V | V | Experimental |
| AWS SQS | V | V | Experimental |
| AWS SNS | V | Experimental | |
| Azure EventHubs | V | V | Experimental |
| Azure CosmosDB | V | Experimental | |
| GCP Storage Bucket | V | Experimental | |
| HTTP | V | Experimental | |
| MQTT | V | V | Experimental |
| Redis | V | Experimental | |
| AWS DynamoDB | V | Experimental | |
| AWS S3 | V | Experimental | |
| Azure Blob Storage | V | Experimental | |
| Azure Service Bus Queues | V | V | Experimental |
| GCP Cloud Pub/Sub | V | V | Experimental |
| Kubernetes Events | V | Experimental |
Input Bindings
Input bindings are used to trigger your application when an event from an external resource has occured. An optional payload and metadata might be sent with the request.
In order to receive events from an input binding:
- Define the component YAML that describes the type of binding and its metadata (connection info, etc.)
- Listen on an HTTP endpoint for the incoming event, or use the gRPC proto library to get incoming events.
Read the How To section to get started with input bindings.
Output Bindings
Output bindings allow users to invoke external resources An optional payload and metadata can be sent with the invocation request.
In order to invoke an output binding:
- Define the component YAML that describes the type of binding and its metadata (connection info, etc.)
- Use the HTTP endpoint or gRPC method to invoke the binding with an optional payload
Read the How To section to get started with output bindings.