Client
Broadcom
Industry
Enterprise software, API management
Technologies
Google Cloud
AWS
Terraform
Packer
Ansible

Broadcom designs semiconductors and sells infrastructure software to large enterprises. In November 2018 it completed the acquisition of CA Technologies, an enterprise software vendor, and with it took on CA's API management product line, including the API Gateway appliance and its developer portal.
Acquisitions create exactly this kind of project. The acquired product arrives on whatever cloud its previous owner chose, and the new owner has a platform standard of its own. Someone has to move it, without breaking the customers already using it.
Project
The products moved were an API management gateway and portal that Broadcom's customers use to publish and secure their own APIs. SEYA built the Google Cloud infrastructure from code, deployed the gateway and portal, and tested them.
Broadcom chose Google Cloud as the platform for the API management products and decided to move the infrastructure and applications off AWS, where they had been running under CA Technologies. SEYA was asked to help with that migration.
SEYA drafted a cloud-to-cloud migration approach, built the Google Cloud infrastructure with Terraform, Packer and Ansible, deployed and tested the gateway and portal, and took part in the application migrations for the Broadcom product lineup in scope, working alongside Google Cloud's technical account managers.
Deliverables:
A cloud-to-cloud migration approach for the API management gateway and developer portal
Google Cloud infrastructure built with Terraform, Packer and Ansible, so the target environment is reproducible from code
Deployment of the gateway and portal on Google Cloud, followed by testing
Participation in application migrations for the Broadcom product lineup in scope, in coordination with Google Cloud technical account managers
The Challenge
A platform-standardization decision after an acquisition sets a deadline that is not negotiable in the way an internal project might be. Running the same product on two clouds doubles the operational surface, splits the engineering team's attention, and keeps the acquired business on a cost base the acquirer never chose.
The products in question were an API management gateway and its portal: software that Broadcom's enterprise customers depend on to publish and secure their own APIs. The migration therefore had to land the gateway and portal on Google Cloud in a state that could be tested and trusted, while the wider product lineup was moving at the same time.
Our Expertise
SEYA brought prior familiarity with the API management gateway and with Google Cloud, which shortened the discovery phase. Rather than treat AWS resources as things to copy one for one, the team drafted a cloud-to-cloud approach that defined the Google Cloud target first and then mapped the gateway and portal onto it.
The approach was worked through with Google Cloud technical account managers, so platform-specific decisions had the vendor's input before they were built.
Our Solution
SEYA built the Google Cloud infrastructure using Terraform for provisioning, Packer for machine images and Ansible for configuration. The Google Cloud infrastructure is defined in Terraform, Packer and Ansible code, which means Broadcom's platform team can rebuild, extend or audit the estate from those definitions rather than from a console.
On that infrastructure SEYA deployed the API management gateway and the portal, then tested both. In parallel, SEYA took part in the application migrations for the Broadcom product lineup that was in scope for the move.
Value Delivered
For an IT leader absorbing an acquired product line, the useful lesson is the order of operations: define the target platform in code, build it, deploy the product onto it, test, then retire the source. Each stage is checkable, and the code becomes the record of what was built.
Working with the cloud provider's own technical account managers meant architecture decisions on Google Cloud reflected the provider's current guidance, and gave Broadcom a direct line into the platform for anything the migration surfaced.
Building with Terraform, Packer and Ansible from the start left Broadcom with an API management environment that is reproducible, which matters when the same product has to be stood up again for new regions or new customers.
The Result
The API management gateway and portal run on Google Cloud, deployed and tested on infrastructure SEYA built from code.
Application migrations for the Broadcom product lineup in scope were completed as part of the same program, moving the acquired software onto the platform Broadcom had standardized on.
Illustrative: the platform decision came from the acquirer, which is what turned a product hosting choice into a migration with a corporate deadline.
Illustrative: the gateway and portal were SEYA's direct deployment; the product-lineup applications are marked as migrations SEYA took part in.
Illustrative: infrastructure is built and the product deployed before testing, so cutover decisions rest on a tested target rather than a plan.
Illustrative: the three tools are shown as one toolchain producing the environment, with Google Cloud technical account managers involved in the build.
Consolidating acquired products onto one cloud platform?
SEYA can draft the cloud-to-cloud approach and build the target environment in code so your team can test before cutover. Reach us at hello@seyagroup.io.
Contact us
Send an enquiry about a cloud, platform, data, or reliability engagement. Marketing email is a separate choice on the form.