Boomi AtomSphere: Atoms, Molecules, and Integration Clouds
Understand the multi-tenant architecture of Boomi AtomSphere, comparing single-tenant Atoms, high-availability Molecules, and Cloud runtime execution engines.
Key Takeaways
- Boomi separates the central cloud management plane (AtomSphere platform) from distributed execution runtimes (Atoms/Molecules)
- A Boomi Atom is a lightweight single-tenant Java runtime deployed on-premises, in private clouds, or on Boomi Cloud
- A Boomi Molecule is a multi-node, clustered Atom architecture providing high availability, node failover, and load balancing
- Boomi Process execution is visual and shape-driven (Start, Map, Decision, Branch, Route, Try/Catch)
The Diagnostic Context
Boomi (formerly Dell Boomi) pioneered cloud-native Integration Platform as a Service (iPaaS). Its architecture decouples the cloud-hosted visual design and monitoring platform from distributed runtime execution engines known as Atoms.
The Core Technique
The Boomi Architecture: Platform vs Runtime
graph TD
subgraph CloudPlane["Boomi AtomSphere Platform (Cloud Management Plane)"]
UI["Visual Process Designer"]
Deploy["Component Deployment & Versioning"]
Monitor["Process Reporting & Log Dashboard"]
end
subgraph RuntimeLocal["Customer On-Premises / VPC Runtimes"]
Atom1["Local Boomi Atom (Single JVM)"]
subgraph MoleculeCluster["Boomi Molecule (Clustered HA)"]
Node1["Molecule Node 1"]
Node2["Molecule Node 2"]
SharedDisk[("Shared File System NFS")]
Node1 --- SharedDisk
Node2 --- SharedDisk
end
end
subgraph RuntimeCloud["Boomi Managed Cloud Runtimes"]
CloudAtom["Boomi Atom Cloud (Multi-Tenant)"]
end
UI -.->|Deploys Process XML| Atom1
UI -.->|Deploys Process XML| Node1
UI -.->|Deploys Process XML| CloudAtom
Atom1 -->|Outbound HTTPS Tracking Data| Monitor
Node1 -->|Outbound HTTPS Tracking Data| Monitor
CloudAtom -->|Outbound HTTPS Tracking Data| Monitor
Atom vs Molecule vs Atom Cloud
| Runtime Type | Clustering / Nodes | High Availability | Best Use Case | |---|---|---|---| | Boomi Atom | Single node (1 JVM) | No (Restart required if host crashes) | Dev/test environments, lightweight on-premises behind firewalls | | Boomi Molecule | Multi-node cluster sharing NFS storage | Yes (Automatic node failover and load distribution) | Mission-critical production workloads, high-volume transactional pipelines | | Boomi Atom Cloud | Multi-tenant or Single-tenant managed cloud | Yes (Managed by Boomi / AWS) | Pure cloud-to-cloud SaaS integrations (e.g., Salesforce to NetSuite) |
Core Process Flow Shapes in Boomi
- Start Shape: Entry point configuring the inbound connector (e.g., Web Services Server, SFTP, Database, or No Data).
- Map Shape: Transforms source XML/JSON/Flat File profiles into destination profiles using standard functions or custom JavaScript/Groovy scripts.
- Decision Shape: Evaluates a true/false condition based on document values.
- Branch Shape: Executes sequential paths in strict numerical order (Path 1 finishes completely before Path 2 begins).
- Try/Catch Shape: Catches runtime document errors, routing failed documents down the Catch branch for error handling while allowing successful documents to proceed.
Try This Right Now
In Boomi AtomSphere (or reviewing process diagrams), configure a process with a Start Shape (Web Services Server listener), a Branch Shape with 2 paths: Path 1 writes an audit record to a database, and Path 2 maps the payload and dispatches an outbound REST POST to an external billing API.
Tip: Knowledge only becomes capability once you run the prompt yourself.