The Broadcom Continuous Delivery Automation Alternative
Migrate from Broadcom CDA to Cloudomation Engine. Get a solution that you can customize to your exact needs.
- Release & Deployment Automation
- Endless integration possibilities
- Managed Cloud, Managed On-Premise, Self-Hosted
Powerful
Automate complex deployment processes with many dependencies and numerous deployment targets.
Flexible
Integrate software and systems with ready-made connectors, APIs or webhooks.
Grows with you
If your requirements change, Cloudomation Engine changes. Expand your automations at any time.
Broadcom CDA: The Alternative
With Cloudomation Engine there is an alternative that allows you to map the same complexity as with CDA.
- Thanks to the use of Python as the automation language, Cloudomation Engine is much more accessible.
- Create and extend the automations yourself. Gladly with our support, but always with the aim of maintaining your independence from expensive consultants.
- Cloudomation Engine is much lighter in terms of installation and maintenance.
Comparison table: Cloudomation Engine vs. Broadcom CDA
| Feature | Cloudomation Engine | Broadcom CDA |
|---|---|---|
Code-based automation | Custom with Python. | Provider specific script language that must be learned and has limitations. |
Agentless Automation No agent or other component needs to be running on the target system to enable automation. Only accessibility via the network and remote access must be given. | - | |
Installation | Simple. Via Docker Compose. | Complex. Requires many components. Additional licenses required for database backend (Oracle, MS SQL, DB2). |
Maintenance | Easy | Complex |
Git Integration | ||
REST API | ||
Custom REST API | Any data and parameters can be accepted and any responses can be defined. | - |
Custom and dynamic property values | Properties to parameterise distributions and components can be added. The data model describing applications and components is fully customisable. For example, the Version property is a standard property for an application that can be used to parameterize deployments. You can also add custom properties, e.g. "license information", "database backend type", "datacenter location" and "customer information". The data model is fully customizable, so you can add or remove properties. Properties can also be created dynamically during a workflow, e.g. when reading properties from a database that can contain different fields at different times or when certain properties are only created for individual / special deployments. | Can be added. The data model is not customisable. |
Interface mocking Using mock objects for tests to mimic a specific behavior. | - | |
Interface Analysis Gather information about remote systems and run common procedures on them. | Limited | |
Interface monitoring Monitoring of systems. Notification when certain conditions apply. | - | |
Live monitoring Display executions that are currently running or have finished. | ||
Role Based Access Control | ||
Automatic rollback Rollback of already running and running processes. | ||
Snapshots | ||
Scheduling Executions at specific times or time intervals. | ||
Notifications | ||
Plugins | Yes, extensions developed by Cloudomation are available. |
LS telcom has replaced Broadcom CDA with Cloudomation Engine. Learn how the company now implements its release and deployment automation with Cloudomation Engine.
FAQ
A deployment target is a location where software is installed – this can be a single server, but it can also be multiple servers or VMs. There is no limit on the number of deployment targets that can be automated with Cloudomation Engine.
Yes, a component can be deployed to multiple different servers. Multiple components can also be deployed on a single server, or a component can be deployed on its own server while others are deployed on shared ones, etc. How and where the software is deployed is fully customizable.
None. No agents need to be pre-installed on the deployment targets. For example, Cloudomation can connect to a server agentlessly via SSH to install software. Cloudomation can also directly interact with APIs of cloud providers or virtualization technologies to create the infrastructure on which the software is then installed.
Any error-catching logic can be implemented. By default, all connectors pass on errors they encounter, allowing you to define in the Python logic within Cloudomation Engine how to handle these errors. You can also use general error-handling logic that defines how to proceed independently of specific errors (for instance, when it is not known which errors might occur), such as sending notifications.
Logs are stored on the Cloudomation server. There is a log expiry logic that can be customized. Generally, we recommend deleting older logs from the Cloudomation server. A log archiving logic can be implemented to write logs to a log server or an archive.
There are no inherent limits on the software side, but performance heavily depends on the volume and size of the data being transferred. Depending on the amount of data to be transferred, the Cloudomation server may also need to be appropriately “sized”.
Features
The most important features at a glance.
Managed Cloud, Managed On-Premise, Self-Hosted
Decide on your preferred hosting.
Python based
Master complexity with the help of Python. Functional limitations are a thing of the past.
Self-repair mechanisms
Make your automation resilient. With intelligent self-repair mechanisms in the event of errors, through repetitions, user interaction and savepoints.
Git Integration
Use all the version control features
of Git.
Agentless Automation
Skip complicated installations, configuration processes and software management on the target system. Information is transferred without a proprietary agent.
Role Based Access Control
Specify individually the authorizations and who may access functions.
Visualisation
See visually how your automation is behaving. Understand when what how and where an automation is carried out.
Schema validation
Validate data against defined schemas. Ensure that data is converted to the correct data type for further processing.
Secret Management
Store confidential information securely and centrally in a Vault. Secrets are only used during an execution of a flow and are never stored or displayed in Cloudomation Engine.
Tools integration
Integrate software and systems with connectors, webhooks and APIs. Mock, monitor and analyse interfaces and receive notification of changes.
Flexible Scheduling
Python allows you to define the scheduler the way you want it. Set a precise schedule for the execution of a flow: at a fixed or flexible interval (minute, hour, days…) or by querying a third party system.
API-Management
Create and manage REST APIs. Use webhooks at the push of a button.
Connectors
Connectors allow you to connect to systems via standard protocols and interfaces.You can use connectors to create your own integrations with a wide range of different software solutions.
AWS
FTP
FTPS
Git
Google APIs
Hashicorp Vault
IMAP
Kubernetes
LDAP
MS Azure
MS Azure AI
MS SQL
MS Teams
MySQL
OAuth 1 & 2
Open AI
Oracle SQL
PostgreSQL
Powershell
Redis
REST
scp
smb
smtp
SOAP
ssh
WebDAV
XML-RPC
Use Cases
Release Automation
- End-to-end automation of the entire release process
for all release variants - Flexible, growing automation
- Visibility and opportunity to collaborate on the
process for all teams
Continuous Deployment Automation
- Simple modeling of the software, the components and their dependencies
- Visualisation of the deployment process
- Lightweight platform
Start now with Cloudomation Engine
- Reliable release and deployment automation
- Instantly connect to other systems: With connectors for standard APIs
- Adding, removing and changing release variants is quick and easy