The vast majority of our teams have been moving their services into the Whitecastle network.
It‘s almost been a year since we released this new network design to the wider teams at Slack. This has all been depicted in the diagram below. We also connected our old legacy infrastructure to this new infrastructure so that the teams did not have to do a single big-bang migration, and could instead do it gradually.We also built a management VPC that has connectivity to all other VPCs, so that we can use it to host our management services, such as our Chef configuration management server.We built new VPCs across our global AWS regions and connected them all together using the AWS Transit Gateway.
If you have not had an opportunity to read the initial article, I highly recommend you do that before tackling this one.īut first, let’s do a very quick recap. In it, we discussed how Slack’s AWS infrastructure has evolved over the years and the pain points that drove us to spin up a brand-new network architecture redesign project called Whitecastle. About a year ago, I wrote a blog post called Building the Next Evolution of Cloud Networks at Slack.
0 kommentar(er)
