Does Utilihive Support the “Enterprise Integration Patterns”?

For many years, the book, "Enterprise Integration Patterns" by Gregor Hohpe and Bobby Woolf, has served as a reference guide for integration developers. In the book, various patterns for integration design are presented. Despite the advent of more modern and lightweight iPaaS offerings in the market and the rise of cloud integration, most of the patterns described in the book are still very relevant today.   

Utilihive supports the most relevant Enterprise Integration Patterns (EIP) in its Utilihive (F)Lowcode DSL. The Utilihive (F)Lowcode DSL is used to model data flows, orchestrate and configure their processors to support the defined Integration Styles, Message Systems, Messaging Channels, Message Construction, Message Routing, Message Transformation or Messaging Endpoints.   

System Management is built into the Utilihive platform. Utilihive comes with big data log analytics capabilities. This provides authorized users access to the message history, message store and to advanced management functions to resubmit or correct failing messages.  

Utilihive supports: 

• Different EIP through its built-in integration artefacts called processors in the Utilihive (F)Lowcode DSLs
• Different integration styles such as file transfer, messaging, streaming, (shared) database or remote procedure calls
• Push and pull integrations both inbound and outbound

• Reliable messaging with guaranteed delivery
• Event driven integration
• Point-to-point, fire & forget, request & reply, publish & subscribe channels
• Configurable error handling in the form of dead letter or failed message channels
• Various processors to construct different message types (including command, document, event, callback with return addresses, and more)

• Correlation of messages and/ or events
• Various (configurable) artefacts to filter, route (i.e. content based router) or distribute messages/ data to both static and dynamic lists of recipients
• Splitting, aggregation and re-sequencing of messages/ data
• Data mappings, transformations or data processing
• Protocol mediations

For more detailed information we refer you the official Enterprise Integration Patterns website.