Inbox ingress is the durable intake edge for commands. It receives broker deliveries, maps headers to inbox metadata, and writes InboxEnvelope rows through IInbox.AcceptAsync or IInbox.AcceptBatchAsync.
Ingress does not execute handlers. Handler execution starts later in the inbox processor.
flowchart LR P[Publisher] --> B[Broker destination] B --> C[IMessageConsumer] C --> L[TransportInboxIngressConsumer] L --> H[TransportInboxIngressHandler] H --> I[IInbox Accept] I --> S[(Inbox store)] S --> PR[PipelinedInboxProcessor] PR --> D[IInboxDispatcher] Package Dependency role Purpose LiteBus.Inbox.IngressFeature bridge Shared handler, consumer loop, mapper, ack policy, telemetry LiteBus.Inbox.Ingress.AmqpFeature bridge RabbitMQ and LavinMQ ingress adapter LiteBus.Inbox.Ingress.KafkaFeature bridge Kafka ingress adapter LiteBus.Inbox.Ingress.AzureServiceBusFeature bridge Service Bus ingress adapter LiteBus.Inbox.Ingress.AwsSqsFeature bridge SQS ingress adapter LiteBus.Inbox.Ingress.InMemoryFeature bridge In-process ingress adapter for fast tests and local development
Broker Maturity Why this tier Main current gaps AMQP GA Deepest live-broker ingress matrix and native queue declaration controls Requeue-off poison drain still untested on RabbitMQ/LavinMQ Kafka Beta End-to-end and failure paths exist No dedicated requeue-off matrix, no dedicated duplicate MessageId matrix, no explicit ack-failed metric assertion AWS SQS Beta Strong ingress matrix, including requeue on/off and idempotency paths Ack-failed metric assertion and FIFO-specific semantics are not covered Azure Service Bus Beta End-to-end and failure coverage on emulator, plus requeue-enabled path No duplicate MessageId matrix, no requeue-off matrix, limited header edge-case matrix InMemory GA (test adapter) Fast deterministic matrix for shared ingress semantics Not a cross-process transport, no broker-native edge semantics
Behavior AMQP Kafka AWS SQS Azure Service Bus InMemory Default RequeueOnFailure true true true true true Exposes shared Safety options yes yes yes yes yes Exposes batch accept through Safety yes yes yes yes yes Native receive control AMQP prefetch none receive batch size prefetch and callback concurrency none Broker declaration options on ingress options yes no no no no Cross-broker identity and idempotency defaults broker-scoped broker-scoped broker-scoped broker-scoped broker-scoped
Executor Folder scope What it proves for ingress LiteBus.Inbox.UnitTestsIngress/, Ingress/Amqp/Mapper, handler, consumer, ack policy, AMQP registration and AMQP handler mapping LiteBus.Durable.IntegrationTestsIngress/<Broker>/, Registration/Broker end-to-end intake, failure handling, selected idempotency and requeue behavior, registration smoke LiteBus.Storage.IntegrationTestsPostgreSql/AMQP ingress with PostgreSQL backing store and duplicate broker delivery idempotency
Coverage gaps described in broker pages follow the ingress matrix in Integration tests .
Limit Notes Event ingress Ingress writes commands to inbox. Event publishing stays in outbox dispatch. Exactly-once side effects Intake is at-least-once with idempotent accept. Handler side effects still need application idempotency where required. Broker health probes Ingress registers background work. Health probes live in hosting and diagnostics modules. One generic UseTransportIngress Broker adapters stay split by package to avoid pulling every SDK into every app.
