As an Integration Platform as a Service, eMagiz is used to realize data and application integrations. eMagiz offers three integration patterns, which as a solid technical foundation can solve any use case. These integration patterns are: Messaging, API Gateway, and Event Streaming. Each integration pattern has its own application area and advantages and disadvantages. eMagiz offers the flexibility to deploy these patterns from one platform, whereby hybrid solutions are also possible. However, the strength of an integration platform lies not only in the technological component but also in the way this functionality is offered to the user.
Click on the features & patterns for more information
Canonical Data Model (CDM)
The CDM is a central data model that holds all the entities and attributes used in all the integrations. The CDM functions as a single view and language for the data models and entities that are used in the clients' environment. Compiling the CDM is often done in the first phase of the platform configuration.
eMagiz is a cloud-native platform. This means that the environment in which integrations are developed runs in the cloud. eMagiz is standardized on cloud environments to keep such environments reliable, secure, and scalable.
Solution architecture refers to the idea of connecting the architecture directly with the business problem, in order to create an effective and scalable solution. In the context of eMagiz, this refers to the way in which different software components are distributed across the eMagiz Cloud and across the customers' infrastructure.
eMagiz can be used throughout the enterprise to model all kinds of integrations around different internal applications and systems. You can also use it to map external data and applications that make contact with internal data and applications. Landscape management is essential for maintaining an overview and understanding of all connections.
Monitoring & alerting
This feature offers the possibility to take control of your complex integration landscape and to react immediately in case of anomalies. Monitoring & alerting is used, among other things, to discover abnormal behavior, set notifications, open logs and metrics side by side, and investigate incidents.
This feature has been developed to support the developer with a fast and streamlined development process, to ensure that all information is documented and that the value for the business is achieved.
Loose coupling is the key for event streaming. Usually there are many Publishers of data and many subscribers who get that data to their service or application. Publishers and subscribers do not need to be aware of each other - the data can be published on a specific Topic (that is where the publisher puts the data and the subscriber retrieves the data).. For more information on the pattern event streaming, click on the button in the figure or go to this page.
API’s (application programming interfaces) play a crucial role in communication between applications, systems and users. APIs are mainly applicable for innovative, externally oriented systems that are part of a distributed application landscape. An API gateway is a central component in which all APIs can be registered, developed and managed easily and efficiently. For more information on the pattern API gateway, click the button in the figure or go to this page.
The messaging pattern is used to exchange messages and data packages reliable, (s) synchronous, and flexible between applications. With the help of a messaging integration, a message (= a data package to be sent between two applications) can be transformed and enriched in terms of content, format, and protocol. This allows organizations to effectively integrate any application, regardless of the underlying technology. For more information on the pattern Messaging, click the button in the figure or go to this page.