StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Deployment
  4. Server Configuration And Automation
  5. Go.CD vs Terraform

Go.CD vs Terraform

OverviewDecisionsComparisonAlternatives

Overview

Terraform
Terraform
Stacks22.9K
Followers14.7K
Votes344
GitHub Stars47.0K
Forks10.1K
GoCD
GoCD
Stacks205
Followers325
Votes207
GitHub Stars7.3K
Forks980

Go.CD vs Terraform: What are the differences?

Introduction

Here, we will discuss the key differences between Go.CD and Terraform.

1. Resource Orchestration vs Continuous Delivery: Go.CD is primarily a continuous delivery tool that focuses on managing and automating the software delivery process. It provides end-to-end visibility and control over the entire delivery pipeline. On the other hand, Terraform is a resource orchestration tool that focuses on infrastructure provisioning and management. It allows you to define and manage your infrastructure as code, making it easier to provision, manage, and update resources across various cloud providers.

2. Pipeline-based vs Infrastructure-based: Go.CD is based on the concept of pipelines, where you define a series of stages and tasks required to build, test, and deploy software. It provides a visual representation of the pipeline and allows for easy monitoring and management. Terraform, on the other hand, is infrastructure-based, where you define and manage resources such as virtual machines, networks, and storage. It focuses on the infrastructure layer and allows for the creation and management of resources in a declarative manner.

3. Deployment vs Infrastructure Configuration: Go.CD focuses on the deployment aspect of software delivery, providing features for managing deployments, rolling upgrades, and rollback capabilities. It allows for easy management and tracking of deployments across environments. In contrast, Terraform primarily focuses on infrastructure configuration and management. It enables the provisioning and management of infrastructure resources in a consistent and deterministic manner.

4. Multi-platform vs Cloud-focused: Go.CD is a multi-platform tool that supports various operating systems and can be used for deploying software on a wide range of platforms. It provides integrations with popular tools and helps in managing the entire software delivery process. Terraform, on the other hand, is cloud-focused and is primarily used for provisioning and managing resources on cloud platforms such as AWS, Azure, and Google Cloud. It provides a unified interface for managing cloud infrastructure across different clouds.

5. Workflow vs Infrastructure as Code: Go.CD allows for defining complex deployment workflows and automating the entire software delivery process. It provides features like parallel and sequential execution, manual triggers, and supports complex branching and merging strategies. Terraform, on the other hand, follows the concept of infrastructure as code, where you define your infrastructure in a declarative manner using a domain-specific language. It allows for versioning, collaboration, and reuse of infrastructure configurations.

6. Built-in vs Third-party integrations: Go.CD provides a range of built-in integrations with popular tools and frameworks such as Jenkins, GitHub, and Docker. It allows for seamless integration with existing tools and helps in automating the software delivery process. Terraform, on the other hand, has a vast ecosystem of third-party integrations and plugins. It provides integrations with various cloud providers, configuration management tools, and other infrastructure-related tools, allowing for extensibility and flexibility.

In Summary, Go.CD is a continuous delivery tool focused on deployment and managing the software delivery process, while Terraform is a resource orchestration tool focused on infrastructure provisioning and management as code.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Terraform, GoCD

Sung Won
Sung Won

Nov 4, 2019

DecidedonGoogle Cloud IoT CoreGoogle Cloud IoT CoreTerraformTerraformPythonPython

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

2.25M views2.25M
Comments
Timothy
Timothy

SRE

Mar 20, 2020

Decided

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.
385k views385k
Comments
Daniel
Daniel

May 4, 2020

Decided

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.

426k views426k
Comments

Detailed Comparison

Terraform
Terraform
GoCD
GoCD

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.

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.;Execution Plans: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure.;Resource Graph: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.;Change Automation: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what Terraform will change and in what order, avoiding many possible human errors
Model complex workflows with dependency management and parallel execution; Easy to pass once-built binaries between stages; Visibility into your end-to-end workflow. Track a change from commit to deploy at a glance; Manual triggers allow deployment any version at anytime. And it's securable and auditable; Run tests written in most languages or frameworks, provides informative testing report; Compare both files and commit messages across any two arbitrary builds; Eliminate Bottlenecks by providing trivial parallel execution across pipelines, platforms, versions, branches, etc.; Easily reuse pipeline configurations via template system.
Statistics
GitHub Stars
47.0K
GitHub Stars
7.3K
GitHub Forks
10.1K
GitHub Forks
980
Stacks
22.9K
Stacks
205
Followers
14.7K
Followers
325
Votes
344
Votes
207
Pros & Cons
Pros
  • 121
    Infrastructure as code
  • 73
    Declarative syntax
  • 45
    Planning
  • 28
    Simple
  • 24
    Parallelism
Cons
  • 1
    Doesn't have full support to GKE
Pros
  • 32
    Open source
  • 27
    Pipeline dependencies
  • 25
    Pipeline structures
  • 22
    Can run jobs in parallel
  • 20
    Very flexible
Cons
  • 2
    Horrible ui
  • 2
    Lack of plugins
  • 1
    No support
Integrations
Heroku
Heroku
Amazon EC2
Amazon EC2
CloudFlare
CloudFlare
DNSimple
DNSimple
Microsoft Azure
Microsoft Azure
Consul
Consul
Equinix Metal
Equinix Metal
DigitalOcean
DigitalOcean
OpenStack
OpenStack
Google Compute Engine
Google Compute Engine
Docker
Docker
Kubernetes
Kubernetes
Slack
Slack

What are some alternatives to Terraform, GoCD?

Jenkins

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

Ansible

Ansible

Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.

CircleCI

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

Chef

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.

TeamCity

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

Capistrano

Capistrano

Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana