Messaging & Service Bus

0 questions

You will learn the libraries that actually carry messages, whether inside one process or across services: mediator dispatch, full service buses, and the delivery, contract and failure concerns wrapped around them. Interviewers ask because once a system stops being a single request and response, the messaging layer is where the hard design decisions live.

questions

no questions here yet

this part of the tree is still being written

>

0 questions in this topic or below it

browse the rest of Backend →

explore

MassTransitempty
- Consumers & Receive Endpointsempty
- State Machine Sagasempty
- Transports & Bus Configurationempty
- Test Harnessempty
NServiceBusempty
- Endpoints, Handlers & Routingempty
- Sagas & Timeoutsempty
- Recoverability & Outboxempty
MediatRempty
- Requests & Notificationsempty
- Pipeline Behaviorsempty
Library-Level Messaging Patternsempty
- Point-to-Point vs Pub/Sub Consumptionempty
- Request-Reply over Messagingempty
- Sagas & Process Managers in Codeempty
- Outbox & Inbox Implementationempty
- Large Payloads & Claim Checkempty
- In-Process Mediatorempty
Delivery Semantics & Failure Handlingempty
- Acknowledgement Modes & Redeliveryempty
- Retry & Backoff Policiesempty
- Dead-Letter Queues & Poison Messagesempty
- Ordering from the Consumer Sideempty
- Prefetch, Concurrency & Backpressureempty
Message Contracts & Versioningempty
- Message Versioningempty
- Validating Messages in Consumersempty
- Message Envelope & Headersempty