Bindings overview

    Using bindings, you can trigger your app with events coming in from external systems, or interface with external systems. This building block provides several benefits for you and your code:

    • Remove the complexities of connecting to, and polling from, messaging systems such as queues and message buses
    • Keep your code free from SDKs or libraries
    • Handle retries and failure recovery
    • Switch between bindings at run time
    • Build portable applications where environment-specific bindings are set-up and no code changes are required

    For a specific example, bindings would allow your microservice to respond to incoming Twilio/SMS messages without adding or configuring a third-party Twilio SDK, worrying about polling from Twilio (or using websockets, etc.).

    Bindings are developed independently of Dapr runtime. You can view and contribute to the bindings here.

    In order to receive events from an input binding:

    1. Define the component YAML that describes the type of binding and its metadata (connection info, etc.)

    Read the page to get started with input bindings.

    In order to invoke an output binding:

    1. Define the component YAML that describes the type of binding and its metadata (connection info, etc.)
    2. Use the HTTP endpoint or gRPC method to invoke the binding with an optional payload

    Read the Use output bindings to interface with external resources page to get started with output bindings.

    Last modified September 17, 2021 : Merge pull request #1757 from georgestevens99/1440SecretKeyRefExplanation (620a5f8)