Learn more about Capsules, a feature that lets you create integration flows that can be encapsulated and reused in the Digibee Integration Platform.
Capsules are a set of configured components that are encapsulated to be reused in Pipelines construction. Since they allow modularizing business logic, it becomes easier to manage, maintain, and update individual parts of the system, as well as decrease the pipeline building time.
It's like the components available in the Platform are atoms and the Capsules are molecules that group the atoms into more complex tasks to solve a specific issue.
To use a Capsule, follow these steps:
The essence of Capsules is to provide the market with ready-made, tested and validated integrations to get a better internal or external connection in a documented way. It allows a company to modernize its IT and its partner companies to use offers with security and simplicity.
For example, imagine a company where there are multiple relevant data flows for all areas – authentication, customer requests, inventory queries, and others. For these data flows, it’s possible to create pipelines that distribute the services, but it’s also necessary to document, catalog and maintain the deployed pipeline.
By making the flows from any part of a pipeline more accessible, you can set broader business goals. That's why we developed this functionality that brings together flows and makes them reusable and self-documenting, just like our core components. This way, the flows become easier to use and familiar across your organization – all you need to do is consult the components palette.
The Capsules contain the core components of the Digibee Integration Platform, which means they have all the functionality that these components offer.
When a Capsule is created, you can specify the parameters, the documentation, the interface, and also the instructions for use. The freedom to create Capsules comes with all these features and the documentation remains in the component itself.
Yes. It’s possible to have Capsules with ready integration between a company's system and its partner. Capsules can also be reused for other partners with similar use cases.
For example, a bank can use a Capsule for microcredit with the POS (Point of Sale) systems of different pharmacy chains.
Yes. When cloud migration happens, it’s very important to have coexistence strategies with on-premises. For example, by incorporating Capsules into this strategy, it’s possible to develop solutions that register data on-premises, in the cloud, or both.
In addition, the Digibee Integration Platform has a wide range of Capsules available for cloud native solutions.
Does the Digibee Integration Platform provide support for expanding my business system with Capsules?
Yes. The Digibee Integration Platform has a Delivery team specialized in Capsules that supports all customers in the creation and development of projects for any company, including the creation of public Capsules (created at the request of the company).
The platform doesn’t set quantitative limits on the components that can be used in the pipeline, whether they are core components or Capsules. However, the pipeline has limits, such as the number of concurrent executions, timeout, and controlled capacity in deployment when SMALL, MEDIUM, or LARGE is selected.
Since Capsules are reusable components in pipelines, we use the output contract of the JSON Schema specification to ensure that pipelines have clarity and security of response information. In addition, the output contract also supports Capsule versioning automation.
When you add a Capsule to your pipeline, you link it to the "Major" or "Minor" version of the Capsule. The "Fix" version is not linked because the pipeline always automatically gets the latest "Fix" version when a new deployment is made or when the Execution panel is run on the pipeline canvas.
As mentioned in the Capsules versioning documentation, the "Fix" version is only changed if the change does not affect the pipeline. Pipelines are not affected or updated by "Major" or "Minor" versions of a Capsule that is part of its compilation. To use this Capsule, an Integration Analyst responsible for the pipeline must apply it manually.
These components are native resources of your realm. Therefore, they are automatically authorized for the controlled context of the realm. Since a Capsule can be created for use by other realms, it's not possible to authorize access to data from these components within the Capsule.