In case your integration environment demands you to connect resources behind a firewall, like your database, for example, or other local applications, you need to install Atoms locally. You can either install Atoms directly into your local network which is required for an on-premise deployment model, or you can use one in the cloud directly for in-cloud deployment. ![]() There are multiple ways to use Atoms within the Boomi atmosphere. The figure below can help you understand the in-depth working mechanism of a Boomi Atom. The components include connectors, transformation rules, and processing logic. After deploying your integration operations to the Atom, it will include all the essential components that you need to execute your processes from end-to-end. We can define a Boomi Atom as a lightweight, dynamic runtime engine. Alternatively, on-premise deployment models that install local Atom components to run are needed especially when the customer has data compliance requirements that restricts data from leaving their firewall or location, or we need to access an older on-premise database or local system. In over 90% of our projects, customers use the In-Cloud deployment model. When implementing Boomi in your organization, it’s essential to know when to use Boomi Atoms and Molecules. ![]() On-premise deployment: If any of the integration endpoints are within a corporate network, it is an on-premise deployment model.In-cloud deployment: All the points of integration are within cloud-based applications in this model. ![]() Boomi provides a leading cloud-based integration service which supports two types of deployment models:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |