Google Cloud Deployment Manager聽vs聽Terraform

Need advice about which tool to choose?Ask the StackShare community!

Google Cloud Deployment Manager

21
82
+ 1
5
Terraform

10.8K
8K
+ 1
318
Add tool

Google Cloud Deployment Manager vs Terraform: What are the differences?

Developers describe Google Cloud Deployment Manager as "Create and manage cloud resources with simple templates". Google Cloud Deployment Manager allows you to specify all the resources needed for your application in a declarative format using yaml. On the other hand, Terraform is detailed as "Describe your complete infrastructure as code and build resources across providers". With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

Google Cloud Deployment Manager and Terraform can be primarily classified as "Infrastructure Build" tools.

Terraform is an open source tool with 17.4K GitHub stars and 4.77K GitHub forks. Here's a link to Terraform's open source repository on GitHub.

Decisions about Google Cloud Deployment Manager and Terraform
Kirill Shirinkin
Cloud and DevOps Consultant at mkdev | 3 upvotes 路 63.8K views

Ok, so first - AWS Copilot is CloudFormation under the hood, but the way it works results in you not thinking about CFN anymore. AWS found the right balance with Copilot - it's insanely simple to setup production-ready multi-account environment with many services inside, with CI/CD out of the box etc etc. It's pretty new, but even now it was enough to launch Transcripto, which uses may be a dozen of different AWS services, all bound together by Copilot.

See more

Because Pulumi uses real programming languages, you can actually write abstractions for your infrastructure code, which is incredibly empowering. You still 'describe' your desired state, but by having a programming language at your fingers, you can factor out patterns, and package it up for easier consumption.

See more
Sergey Ivanov
Overview

We use Terraform to manage AWS cloud environment for the project. It is pretty complex, largely static, security-focused, and constantly evolving.

Terraform provides descriptive (declarative) way of defining the target configuration, where it can work out the dependencies between configuration elements and apply differences without re-provisioning the entire cloud stack.

Advantages

Terraform is vendor-neutral in a way that it is using a common configuration language (HCL) with plugins (providers) for multiple cloud and service providers.

Terraform keeps track of the previous state of the deployment and applies incremental changes, resulting in faster deployment times.

Terraform allows us to share reusable modules between projects. We have built an impressive library of modules internally, which makes it very easy to assemble a new project from pre-fabricated building blocks.

Disadvantages

Software is imperfect, and Terraform is no exception. Occasionally we hit annoying bugs that we have to work around. The interaction with any underlying APIs is encapsulated inside 3rd party Terraform providers, and any bug fixes or new features require a provider release. Some providers have very poor coverage of the underlying APIs.

Terraform is not great for managing highly dynamic parts of cloud environments. That part is better delegated to other tools or scripts.

Terraform state may go out of sync with the target environment or with the source configuration, which often results in painful reconciliation.

See more

I personally am not a huge fan of vendor lock in for multiple reasons:

  • I've seen cost saving moves to the cloud end up costing a fortune and trapping companies due to over utilization of cloud specific features.
  • I've seen S3 failures nearly take down half the internet.
  • I've seen companies get stuck in the cloud because they aren't built cloud agnostic.

I choose to use terraform for my cloud provisioning for these reasons:

  • It's cloud agnostic so I can use it no matter where I am.
  • It isn't difficult to use and uses a relatively easy to read language.
  • It tests infrastructure before running it, and enables me to see and keep changes up to date.
  • It runs from the same CLI I do most of my CM work from.
See more

Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

Check Out My Architecture: CLICK ME

Check out the GitHub repo attached

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Google Cloud Deployment Manager
Pros of Terraform
  • 2
    Automates infrastructure deployments
  • 1
    Infrastracture as a code
  • 1
    Fast deploy and update
  • 1
    Easy to deploy for GCP
  • 108
    Infrastructure as code
  • 72
    Declarative syntax
  • 44
    Planning
  • 27
    Simple
  • 24
    Parallelism
  • 7
    Cloud agnostic
  • 6
    It's like coding your infrastructure in simple English
  • 5
    Well-documented
  • 4
    Automates infrastructure deployments
  • 4
    Immutable infrastructure
  • 4
    Platform agnostic
  • 3
    Portability
  • 3
    Extendable
  • 3
    Automation
  • 2
    Scales to hundreds of hosts
  • 2
    Lightweight

Sign up to add or upvote prosMake informed product decisions

Cons of Google Cloud Deployment Manager
Cons of Terraform
  • 1
    Only using in GCP
  • 1
    Doesn't have full support to GKE

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Google Cloud Deployment Manager?

Google Cloud Deployment Manager allows you to specify all the resources needed for your application in a declarative format using yaml.

What is Terraform?

With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Google Cloud Deployment Manager?
What companies use Terraform?
See which teams inside your own company are using Google Cloud Deployment Manager or Terraform.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Google Cloud Deployment Manager?
What tools integrate with Terraform?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

+22
17
13408
+42
52
19818
What are some alternatives to Google Cloud Deployment Manager and Terraform?
Chef
Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.
AWS CloudFormation
You can use AWS CloudFormation鈥檚 sample templates or create your own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run your application. You don鈥檛 need to figure out the order in which AWS services need to be provisioned or the subtleties of how to make those dependencies work.
Packer
Packer automates the creation of any type of machine image. It embraces modern configuration management by encouraging you to use automated scripts to install and configure the software within your Packer-made images.
Pulumi
Pulumi is a cloud development platform that makes creating cloud programs easy and productive. Skip the YAML and just write code. Pulumi is multi-language, multi-cloud and fully extensible in both its engine and ecosystem of packages.
AWS Cloud Development Kit
It is an open source software development framework to model and provision your cloud application resources using familiar programming languages. It uses the familiarity and expressive power of programming languages for modeling your applications. It provides you with high-level components that preconfigure cloud resources with proven defaults, so you can build cloud applications without needing to be an expert.
See all alternatives