Complexity plays no role with the integration pattern Messaging

Messaging is one of the integration patterns within the eMagiz iPaaS and is used by many customers as the default pattern for integrating applications, services and data.

What is Messaging?

An organization always uses multiple applications, these are built on different platforms and use different protocols. It is essential for business operations that these applications can exchange data with each other. Messaging is used to exchange messages and data packets reliably, (a)synchronously and flexibly between applications. 

Waarom Messaging met eMagiz?

Easily connect Legacy or other applications and systems regardless of format or protocol

Reduce time-to-market for integrations

Improve your data quality & realize a reduction in errors

One clear overview of the integration landscape

Easily and reliably exchange and transform data to any format or protocol


To facilitate the messaging integration pattern, eMagiz uses modern technical frameworks such as ApachMQ Artemis and ApacheQpid. The integration pattern requires a distributed technical architecture, is cloud agnostic and functions both in the cloud and on-premises.

Voor het berichtenverkeer maakt het platform gebruik van het VETRO principe (Validate, Enrich, Transform, Route & Operate). Door dit principe toe te passen streeft eMagiz ‘loose-coupling’ tussen applicaties na en faciliteert het betrouwbare data uitwisseling tussen verschillende applicaties en systemen. Loose-coupling betekent dat de (bericht)definities van systemen en applicaties niet direct met elkaar zijn verbonden (zoals wel het geval is bij point-to-point connecties). Door gebruik te maken van een CDM (centraal data model) zijn data en berichten herbruikbaar. Hierdoor is het integratielandschap schaalbaar en is er meer controle over de data.

Hybrid use of integration patterns

The eMagiz iPaaS is capable using the integration patterns Messaging, API gateway and event streaming in a hybrid way. This provides a unified user experience and gives developers a single interface to work with. For example, within eMagiz it is possible to use an API gateway for synchronous API operations and then redirect the request to an asynchronous messaging stream to communicate with legacy systems.

A Messaging usecase

Huuskes, supplier, producer and knowledge partner in food and beverages for healthcare and corporate catering has fully integrated new and existing applications with each other using the eMagiz message broker. This enables them to connect faster with new systems and clients by working with industry standards, they now have a lower error rate and the number of failed orders has been reduced to an absolute minimum. Read how the eMagiz platform has contributed to more user-friendliness and transparency to clients and how the number of manual operations has been reduced.

Messaging in a nutshell


Synchronous vs. asynchronous traffic

Synchronous traffic refers to data traffic where a response to the initial message is required. This means that the receiver of the message immediately responds and informs about the processing of the message and/or request. This is applicable, for example, in a production process where the process cannot start until sent message (for example, an order) is accepted by the receiving system.

Asynchronous traffic refers to data traffic where a response to the initial message is not required. The sending system can send data to the receiving system and an immediate response is not required. An example of asynchronous data traffic is uploading files to a cloud, where the sender uploads a file and the receiver can download and view files at a later time. 

Both types of traffic are supported in the eMagiz platform.