• Guides
  • Api Reference
  • FAQ
  • Guides
  • Triggers
  • Service Bus Triggers
  • Message Sessions
Show / Hide Table of Contents
  • Overview
    • Introduction
    • Getting Started
    • Philosophy
    • FAQ
    • Upgrading to 1.0
  • Triggers
    • HTTP Triggers
      • Overview
      • Routing
      • Responses
      • Authorization
      • Claims Mapping
      • Headers
      • Swagger / OpenAPI
    • Service Bus Triggers
      • Queues
      • Topic and Subscriptions
      • Message Properties
      • Message Sessions
    • Cosmos DB
      • Overview
      • Error Handling
    • SignalR
    • Timer Triggers
    • Azure Storage Triggers
      • Queues
      • Blobs
    • Event Hub Triggers
  • Output Bindings
  • Cross Cutting Concerns
    • Connection Strings
    • IoC Containers
    • Logging
    • Trigger Contexts
    • Validation
    • Serialization
    • Suggested Solution Structure
  • Contributing
    • Compiling
    • Debugging

Message Sessions

Function Monkey supports (FIFO message sessions)[https://docs.microsoft.com/en-us/azure/service-bus-messaging/message-sessions] for both message processing and output triggers.

To enable on a Service Bus queue or subscription function set the isSessionEnabled parameter to true. For example:

.ServiceBus(serviceBus => serviceBus
    .QueueFunction<ServiceBusSessionIdQueueCommand>("myqueue", true)
)

To specify the message ID in a service bus output binding you need to supply the session ID in the command response and tell Function Monkey which property contains the ID. For example:

.HttpRoute("outputBindings", route => route
    .HttpFunction<MyCommand>("/toServiceBusQueueWithResultSessionId")
    .OutputTo.ServiceBusQueue<MyCommandResult>("myqueue", result => result.SessionId)
)
  • Improve this Doc
  • 0 Comments
Back to top Copyright © 2018 James Randall