How cloud agnosticism can help you make the monumental transition between cloud services
Cloud agnosticism is one of the most underrated advantages to deploying with Spinnaker, which powers the Core of Armory’s Platform. Spinnaker achieves this is by working with cloud abstractions such as:
- Individual servers
- Server groups
- Load balancers
- Network/security groups
- Images and applications
- Deployment strategies
This forward-thinking architectural design allows Spinnaker to work with any existing or future cloud provider. For instance, Spinnaker support for Kubernetes, originally built by the Google engineering team, offers greater insight into the health of a Kubernetes cluster as well as more powerful deployment capabilities (i.e., multiple deployment strategies), through Spinnaker than through the Kubernetes API. And that cloud provider is now being updated by Google and Armory to be even more powerful.
This uniform approach to cloud deployments is instrumental to any company making the monumental change from traditional deployments of monolithic apps in data centers (stage 1 & 2 in this chart) to cloud-native, continuous delivery of microservices (stage 3).
This cloud agnosticism is also essential for companies changing cloud service providers. As illustrated in the case of MakerBot, which was able to utilize Armory’s Core Platform, powered by Spinnaker, to transition from Amazon’s ECS to Google’s Kubernetes six months ahead of schedule.