{{announcement.body}}
{{announcement.title}}

A Journey From MuleSoft to Serverless Integration

DZone 's Guide to

A Journey From MuleSoft to Serverless Integration

In the current highly volatile market trend the cost optimization, infinite scalability, and agile development tools are vital.

· Integration Zone ·
Free Resource

mulesoft and kumologica

In the current highly volatile market trend the cost optimizationinfinite scalability, and agile development tools are very vital for any enterprise digital roadmap. The fast-growing trend of FaaS world with AWS Lambda, Google Cloud function, and Azure Fn has already received recognition of small, medium, and large enterprises and this indicates that the move from the iPaaS to FaaS is natural and unavoidable. This move opens a new world of Serverless Integration.

The key features of serverless integration are:

Infrastructure Ready — No need to provision or manage servers.

Scalability — Services will automatically scale to support the rate of the incoming request, including the ability to scale to zero.

Cost-Efficient — Leverage the subsecond metering of your cloud provider to reduce cost. Pay only for integration services only when they run.

Quick turn around — Enterprise can now focus 100% on functionality and make quick changes based on customer feedback.

In this article, we are going to migrate an existing Mulesoft flow into Kumologica.

You can learn more about Kumologica in this medium article or subscribe to our YouTube channel for the latest videos.

Use Case

In this use case, we will be building a simple ItemAvailability API flow which will invoke an external system (warehouse unit) via HTTP rest endpoint. Based on the item type field in the request, the request will be routed to the appropriate warehouse unit. Warehouse unit A responds in XML format whereas warehouse unit B responds in JSON format. The response from the warehouse units will be transformed into a canonical data structure in JSON format.

item availability

Below is the flow logic that will be implemented on Kumologica and MuleSoft.

item request

Implementation

Here we are implementing the flow logic provided in the above use case section using Kumologica and MuleSoft.

Note: The implementation covers a flow having a small set of nodes or processors in Kumologica and MuleSoft. For more detailed information you can reach out to us and we can provide you with deep-dive demos.

MuleSoft

The flow represented in the below is a MuleSoft flow built following the above-given flow logic.

error handling

Kumologica

The diagram below represents a Kumologica flow built to mirror the same functionality expressed in the Mulesoft flow.

kumologica

Implementation Dissection

Let’s now analyze and compare every element used in Kumologica and MuleSoft flow on the above show cases implementations. The below table shows the connectors and processors in MuleSoft mapped against the appropriate nodes in Kumologica.

Implementation Dissection

Note: Dataweave is a proprietary technology from MuleSoft for expression-based data mapping whereas Kumologica Datamapper uses JSONata technology for doing the data transformation.

A simple API flow in MuleSoft always starts with an HTTP listener which is ready to accept the request whereas in Kumologica this is done by EventListener node. Any flow in Kumologica is explicitly ended using and EventListener end node. Both Kumologica and MuleSoft has the necessary components to achieve VETRO capabilities. (Validation, Enrichment, Transformation, Routing, and Orchestration)

Kumologica and MuleSoft come with a wide variety of connectors and nodes capable of connecting both legacy systems as well as technology protocols. Visit the following link to know more about each node in Kumologica. https://docs.kumologica.com/docs/references/

Deployment

MuleSoft flows are deployed on CloudHub which is a cloud-based platform for running mule applications. Kumologica applications can be deployed on any cloud provider of your choice that avoids the cloud provider locking.

Kumologica flows are deployed either as a Lambda in AWS or as a function in Google or Azure based on the Kumologica runtime you choose.

Conclusion

This article presents how easy it is to develop an integration flow or an API flow in Kumologica Designer similar to MuleSoft and gaining all the benefits of the Serverless world.

To test the above given ItemAvailability Kumologica flow you can download and import into Kumologica designer.

Topics:
aws, integration, ipaas, low code, microservice, mule 3.9, mule api, mulesoft, serverless

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}