DEV Community

Cover image for Reusing integration blocks in Kumologica
ab73863
ab73863

Posted on

Reusing integration blocks in Kumologica

The key principles of almost all the IT enterprises and startups focussed today are

  • Speed of development
  • Easy maintenance of application
  • Reduced cost and effort of development

Above 3 principles are now strong pillars behind a good digital strategy and critical part of a good innovation team.
Low code development and serverless has already increased the speed of development and reduced the overall cost of ownership of an application but still there is room for further gain. This further gain can be achieved with proper design of a code by considering reusability of certain functionality across different services.

Kumologica gives components which allows the developers to build a reusable functionality easily and at the same time a quick and seamless way for sharing the reusable component with the peer developers or across the team.

In Kumologica you can build a reusable integration block using a processor node. The common functionality or logic that has been identified to be reused across different services or flows can be defined between the processor in node and processor out node.

Scenario

In this scenario developer A builds a service. The team members later find that the service they are developing requires a similar logic. Now we will see how the developer A will build the reusable logic in Kumologica and how it’s going to be shared with his peer developers.

Implementation

Building and exporting the reusable integration block

In order to create the reusable flow we are going to make use of the subflow option under the processor node.
Developer A selecting the reusable logic block and exporting using copy to clipboard. The copied JSON content is shared to the developer.

Importing of integration block

Importing the logic block by peer developers on their designer and refer the block in their main flow using processor node.

Top comments (0)