Unity has a global team across five continents with over six business units that have more than 50 aggregated services managed by different teams. Now what makes this migration journey interesting is that the entire infrastructure and security was managed and enforced by a team of four people. The network design was complex, as every workload had different SLAs and security requirements. Hence, careful network planning was required, from IP addressing to HA, DR, shared services, and security policing. But the hardest part was its enforcement and automated deployment as the team’s requirements changed. This was made possible through a web application created by the Unity team that takes user input and automates project creation, firewall rules, service accounts, and more by triggering a pull request, which further triggers TF code deployment. In addition to this, Unity used only open-source software (Quagga running on VMs and FRRouting router as containers) and cloud routers to connect across different cloud vendors without compromising on enterprise-grade SLA and hence saving money on hardware and license costs.
VPC Network Overview → https://bit.ly/2TYrDtv
Cloud NAT → https://bit.ly/2UhteiX
Next ’19 Architecture Sessions here → https://bit.ly/Next19Architecture
Next ‘19 All Sessions playlist → https://bit.ly/Next19AllSessions
Subscribe to the GCP Channel → https://bit.ly/GCloudPlatform
Speaker(s): Davis Pynadath, Ananth Sundarrajan, Ariel Wei
Session ID: ARC213
product:Cloud Virtual Network,Cloud NAT,Cloud For Enterprise; fullname:Davis Pynadath, Ananth Sundarrajan;
Publisher: Google Cloud
You can watch this video also at the source.