Message-bus architecture
Architecture work focused on the messaging layer supporting high-volume transactions.
High-volume transactions
Untangling a message bus supporting high-volume transactions.
Message-bus architecture and cleanup work for high-volume transactions at the retail business.
DOMAINHigh-volume transactions
ENGAGEMENTArchitecture engagement
ENGINEERING FOCUSMessage bus · Architecture · High-volume transactions
Event producersTransaction sources
Application servicesBusiness events
ENGINEERING LAYERMessage-bus architecture
ConsumersProcess messages
Exception pathInvestigate failures
Architecture cleanup focuses on the messaging layer
Conceptual view of the engineering scope, not an as-built client architecture.
The problem
Back3nd worked on message-bus architecture and cleanup for high-volume transactions at the retail business.
Why engineering mattered
At high transaction volumes, the messaging layer becomes a critical part of the application architecture. Understanding how messages move through the system is essential before changing or cleaning up the architecture.
What we engineered
Architecture cleanup
Cleanup work within the message-bus architecture.
Transaction-focused engineering
Engineering attention on the communication layer used by transactional systems.
Delivered scope
Message-bus architecture and cleanup work supporting the high-volume transaction environment.
LET’S GET TO WORK
Where is technology costing you too much?
Software spend. Repetitive work. Disconnected systems. Let’s find the engineering changes that make a difference.