Dedicated clouds
Boomi’s dedicated cloud service provides a Boomi-managed yet self-service, enterprise-grade runtime environment, designed to streamline integration operations while ensuring maximum performance and robust isolation. Using modern containerization practices and Kubernetes architecture, dedicated clouds eliminate the complexity of infrastructure management, with fully managed support by Boomi included.
Key Features:
- Containerized Runtime Environments: Each Java Virtual Machine (JVM) within the Boomi dedicated cloud operates as an independent, containerized pod within Kubernetes. Compared to traditional shared-node deployments, this architecture delivers multiple benefits, including enhanced performance, isolation, and scalability.
- Single-Tenant, Private Cloud Infrastructure: The dedicated cloud is a single-tenant cloud hosted within a Boomi-managed AWS account. Boomi fully handles all infrastructure components, such as maintenance, upgrades, and monitoring, providing a hassle-free user experience.
- Fully Managed Service: Boomi takes responsibility for the ongoing management of the cloud infrastructure, ensuring that updates, security patches, and performance optimizations are consistently applied without requiring user intervention while providing a self-service option to connect to your clouds. This eliminates the burden of manual management and reduces the risk of downtime or performance degradation.
- Private Connectivity: Increased privacy and security via customizable VPN configuration.
Deployment Considerations for Your Cloud:
Dedicated Cloud Architecture:
- With containerized pods for each JVM, Boomi’s dedicated cloud architecture provides superior isolation and operational flexibility so that one’s behavior doesn’t impact the other.
- Dedicated clouds maintain compatibility with existing Boomi runtimes. Boomi handles migration, deployment, updates, and operational tasks.
Additional Benefits of Dedicated Clouds
While Dedicated clouds have some similarities to self-hosted clouds, they have a few key differences.
Similarities to Self-Hosted Clouds:
- Integration Experience: The Boomi runtime operates the same for Dedicated or Self-Hosted clouds. There’s no change in how processes are developed, deployed, or executed.
- Shared File System: Like local setups, the shared file system is used for persistence.
- JVM Configuration: JVM/heap memory settings remain globally configured for all processes, just as in local deployments.
- Customization: Customers can still define custom connectors and configurations as they would in their local environments.
Unique to dedicated Clouds:
- Isolation: Each customer receives a fully isolated environment, ensuring security and compliance without the overhead of managing physical or virtual infrastructure.
- Predictable Costs: Dedicated clouds are offered at a fixed price, removing the unpredictability of fluctuating infrastructure costs typical of local hosting.
- Automatic Updates: Boomi handles all runtime upgrades, including operating system patches and application updates, ensuring you stay secure and current without manual intervention.
- Enterprise Support: Boomi provides 24/7 support and monitoring for your dedicated cloud, removing the need for in-house expertise to maintain runtime stability.
Prerequisites for Dedicated Clouds
Boomi Platform
To enable the use of the dedicated cloud interface for your Boomi account, you must:
- Purchase the dedicated clouds option
- Grant the “Dedicated Cloud” privilege to user roles in your account’s setup. By default, all Administrators have the Dedicated Cloud privilege already enabled in their accounts.
Understanding Cloud Limits
What role do Cloud Limits play in this architecture? Below, you can find the specific limits for the respective dedicated cloud option.
| Dedicated Cloud Options | Option 1 | Option 2 |
|---|---|---|
| Maximum Runtime Workers | 10 | 25 |
| Runtime Worker Concurrent Executions (per runtime worker) | 20 | 20 |
| Runtime Worker Queue Executions (per runtime worker) | 20 | 20 |
| Scheduled Concurrent Executions | 50 | 100 |
| Monthly data throughput (overage fees may apply) | 50GB | 100GB |
| API Requests Input Size (MB) | 5 MB | 5 MB |
| Maximum process execution time (hr) | 24hr | 24hr |
| Test Log Retention | 1 day | 1 day |
| Production Log Retention | 15 days | 15 days |
| JVM Size | 0.5 GB | 0.5 GB |
Known Limitations
Some dedicated cloud usability enhancements have been identified and will be enhanced in later updates.
- Connectors requiring OS-level configurations (e.g., custom libraries or dependencies) or custom security policies are not supported.
Since Dedicated clouds are built on our elastic execution infrastructure, which is still under active development, there are still some functionalities that have limitations, including:
- Currently, users cannot perform connector browsing using a dedicated cloud. This will be added in a future release.
- Flow Control steps configured with the “Processes” parallel processing option are not supported. This will be addressed in a future release.
