Error Handling
What happens when a message cannot be processed. Draw this one.
- Format.puml
- Length26 lines
- LibraryEnterprise Integration Patterns
The source
26 lines of PlantUML, and pulls in Enterprise Integration Patterns. Copy it, or open the template inside Gnomon and render it as it is.
@startuml
!include https://raw.githubusercontent.com/plantuml-stdlib/EIP-PlantUML/main/dist/EIP-PlantUML.puml
title Error Handling with Dead Letter Channel
MsgChannel(input, "Incoming Messages")
MessageRouter(router, "Message Router")
MsgChannel(valid, "Valid Messages")
InvalidMsgChannel(invalid, "Invalid Messages")
DeadLetterChannel(dlq, "Dead Letter Queue")
ServiceActivator(processor, "Message Processor")
ServiceActivator(errorHandler, "Error Handler")
MessageStore(store, "Message Store")
Send(input, router)
router --> valid : valid
router --> invalid : invalid format
Send(valid, processor)
processor --> dlq : processing error
Send(invalid, dlq)
Send(dlq, errorHandler)
Send(errorHandler, store)
@endumlRender this offline
This template ships in Gnomon and renders on your machine, with no account and nothing sent to a server. The browser editor is free and needs no install.
Others in Enterprise integration pattern diagrams
- Simple MessagingA channel and two endpoints: the vocabulary in miniature.
- Content-Based RouterRoute by message content. Where most integrations start.
- Publish-SubscribeOne publisher, many independent subscribers.
- Splitter-AggregatorSplit a message, process the parts, put them back together.
- Pipes and FiltersA processing chain where each stage is replaceable.
- Request-ReplyAsync messaging that still needs an answer.
- Wire Tap (Monitoring)Observe traffic without changing it: for audit and monitoring.