Integration and Cloud Computing
If you have been working on the Integration space, Cloud Integration is one of the topics you might have heard along with Microservices & Cloud-Native.
What are the different Cloud Adoption strategies?
Do you need Integration in Cloud?
Analyst reports highlight that Multi-Cloud is the preferred strategy among the enterprises. This is mainly because of the SaaS/PaaS offerings with scalable models and seamless upgrade/fix processes at affordable costs.
This also brings up same integration challenges with cloud applications/systems to the enterprise.
Figure 1: Point to Point Integration Maze
- Point to Point Integration Maze in the cloud
- App specific Integration needs
- Security, Monitoring and Governance
- Incompatible technologies, Inconsistent data formats
- Distinct interaction styles, multiple integration patterns
- Multiple personas, infinite endpoints and continuous change
Integration makes independently designed applications/systems work together.
webMethods.io is the next generation of Software AG’s Integration Platform as a Service (iPaaS). webMethods.io combines low-code usability with high control of complex integrations and APIs. With an industry-leading set of 300+ supported connectors to SaaS applications and pre-built integrations (recipes), this multi-function iPaaS integrates apps, data, APIs, B2B and IoT devices.
Integration Scenarios with Cloud:
- Cloud to Cloud: Uni / bidirectional Data synchronization of SaaS applications, Event driven Application Integration. Use certified SaaS connectors and pre-built integrations (recipes).
- Cloud to on-premise (Hybrid Integration): Connect on-premise legacy systems and cloud applications. Re-use the existing implementations, integrations, data and expose the same securely.
- On-premise to Cloud: Connect on-premise with cloud hosted SaaS applications with Cloud Stream connectors.
Consuming to APIs will be more than exposing the APIs in Cloud.
Cloud Deployment Models could be across multiple environments – Cloud (Public/Private), Multi-Cloud, Hybrid Cloud, Cloud and on-premise.
Figure 2: Multi-function iPaaS - webMethods.io, Integration Scenarios
Does Cloud effect the Integration Styles?
Does this happen the same way as of on-prem? Yes and No both. Let’s take a look at the classic integration styles.
Figure 3: Source - Enterprise Integration Patterns - https://www.enterpriseintegrationpatterns.com
File Transfer – Use Cloud storage services instead of file systems, FTP/SFTP on cloud. E.g., Amazon S3, Google Cloud Storage, etc.
Shared Database – Choose the right Cloud Database (DBaaS) for your enterprise needs. E.g., Microsoft Azure Cloud SQL DB, Amazon RDS, etc.
Remote Procedure Invocation – APIs are the center of modern application architecture. Follow Contract first approach (Consumer Driven Contracts) to build your integrations and APIs. Protect APIs using API Gateways. Monetize your APIs.
Messaging – Design application integration using event driven patterns as much as possible (scalable send and forget strategy). Use asynchronous callbacks (webhooks) and workflows. Non-blocking Integration always produce better performance and scalable over the blocking.
Application Integration: Application integration (Process Orchestration/Workflows) is about connecting business applications at a functional level. It’s not simply data sharing, but rather, involves triggering some activity in another application by issuing requests or sending “live” business events. E.g., Create a Zendesk ticket on malfunctioning of a Coffee Vending machine. webMethods.io offers workflow capabilities (built.io) that can be invoked with asynchronous callbacks with a REST endpoint or an event triggers to initiate the application integration.
Classic Integration: Defining Standard Data formats (Canonicals/Document Types), implementation of Integration and APIs (REST/SOAP), Media Types (XML/JSON), scheduled batch integrations, Hybrid Integrations with the on-premise applications are available with flow services within webMethods.io Integration. Re-use Integration/APIs created in your workflows (as mentioned above).
API Management: Securely manage and expose your APIs to third-party developers, partners and other consumers for use in web, mobile and Internet of Things (IoT) applications. Create new business models and enrich your ecosystems with full lifecycle API management.
B2B Integration: Exchange your B2B documents in the cloud—and avoid infrastructure headaches and costs. With webMethods.io B2B, built on the industry-leading webMethods Trading Networks, you can transmit business documents—like purchase orders, invoices and shipping notices—electronically with customers, distributors and trading partners.
webMethods Cloud Container: Cloud Container offers Lift and Shift capabilities to deploy webMethods Integrations to the Cloud. You can use the same set of tools to develop, debug and test integrations for the cloud as you do for on-premises integration using this offering. fix, patch management and scheduled upgrades, and CI/CD support in the cloud are few highlights for this offering.