Build Infrastructure Once and Deploy Anywhere
Define stack configuration on one environment, and authorized admins can easily clone the stack configuration and update some configurations, such as cluster parameters. Admins can target environment settings and deploy the cloned stack to upper environments, such as staging or production environments. Also, in a future release, Admins will be able to clone the stack configuration and deploy it to other cloud environments (after updating target environment settings) such as AWS, Azure, GCP, on-prem, or anywhere else.
Therefore, a Data Platform stack is built once and can be cloned and safely deployed anywhere because the original stack and the cloned stack are from the same Architecture Blueprint. snapblocs enables consistent and templated sandbox development, test, and production environments with increasing levels of operational excellence.
Benefits:
Reuse the same skillsets for development and operations no matter where the stack was built and deployed.
With a build once, deploy anywhere approach significantly reduces time by deploying the same Architecture Blueprint continuously from development to production.
Spend more time trying to solve flaws within business applications instead of troubleshooting replicating Data Platform infrastructure issues. For example, debug the production problems by cloning the production stack into an isolated environment. Install production business applications into the cloned production stack and debug the production problems, not impacting the production stack.
snapblocs provides templated deployments resulting in fewer errors in promoting applications from lower to upper environments using the cloning feature in the snapblocs UI.
1.1-JPE-F
Related Articles
Architecture as Code vs Infrastructure as Code
The ‘as code’ paradigm is about being able to reproduce and/or restore a full environment within minutes based on recipes and automation, managed as code. Therefore, the ‘as Code’ approach provides repeatability, share-ability, versioning in ...
How to deploy a stack
Once configuring a stack following here, you can deploy the stack. To deploy a stack: Click the "Deploy" button on the top of the Stack configuration page. (It would take up to 20 minutes to fully deploy the stack) The stack status will be changed to ...
How to clone a stack
Once configuring a stack following here, you can clone the stack to the same project or a different project. For example, once a stack configuration is created on one project, an authorized user can easily clone the stack configuration and update ...
snapblocs vs. Other Managed Kubernetes Platforms
Most Kubernetes platforms focus on the how of deploying and managing Kubernetes-based infrastructure. What remains, is the task of building business solutions from there. snapblocs also provides this same managed Kubernetes enablement, as do other ...
snapblocs Introduction
Build self-service platforms on Kubernetes in the Cloud snapblocs is a cloud-native deployment platform for configuring, deploying, and managing data platforms across AWS, Azure, Google, and other cloud providers. Create fully automated Day-2 ...