eiPaaS and the distributed architecture

What exactly is an eiPaaS and how is it different from iPaaS? What is distributed architecture?

eiPaaS and the distributed architecture

When talking about integration platforms that are provided as a service, we most commonly use the acronym “iPaaS”. But what exactly is an eiPaaS and how is it different from iPaaS?

EiPaaS stands for “enterprise integration platform as a service” that provides capabilities to enable customers to implement data, application, API and process integration projects involving any combination of cloud and on-premises endpoints. This is achieved by developing, deploying, executing, managing and monitoring integration processes that connect multiple endpoints in various deployment models so that they can work together.

An eiPaaS solution is typically used for cloud service integration (CSI), application-to-application integration (A2A), business-to-business integration (B2B) scenarios and, increasingly, for mobile application integration (MAI) and IoT integration scenarios. Unlike iPaaS solutions, eiPaaS solutions are designed to support enterprise-class integration projects requiring:

• High availability/disaster recovery (HA/DR) • Security • Service-level agreements (SLAs) • Technical support from the provider

What is the distributed architecture?

FRENDS’ architecture is based on something called distributed architecture, where components known as “agents” are deployed to an environment where the integration need is located. The integration development, monitoring and overall management is handled in the FRENDS UI, but the actual integration happens in the agents. This enables one of the key features of FRENDS which is that despite being a cloud service, by defining what is logged and what’s not, we can make sure any sensitive data from the on-premise environments for example, doesn’t end up in the cloud. You decide what functionality gets executed where.

To make things even simpler and efficient, only one agent is needed to communicate with all the systems in one environment (e.g. intranet or in a cloud environment such as Azure or AWS). The agents also communicate with each other, which for example enables seamless data collection from multiple environments/systems into a place where the data is needed.

frendsDistributedArchitecture

Enter your email address to get our newsletter.

Loading...