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

AWS CodeDeploy

349
501
+ 1
38
Terraform

10.6K
8.4K
+ 1
320
Add tool

AWS CodeDeploy vs Terraform: What are the differences?

AWS CodeDeploy: Coordinate application deployments to Amazon EC2 instances. AWS CodeDeploy is a service that automates code deployments to Amazon EC2 instances. AWS CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during deployment, and handles the complexity of updating your applications; Terraform: 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.

AWS CodeDeploy and Terraform are primarily classified as "Deployment as a Service" and "Infrastructure Build" tools respectively.

Some of the features offered by AWS CodeDeploy are:

  • AWS CodeDeploy fully automates your code deployments, allowing you to deploy reliably and rapidly
  • AWS CodeDeploy helps maximize your application availability by performing rolling updates across your Amazon EC2 instances and tracking application health according to configurable rules
  • AWS CodeDeploy allows you to easily launch and track the status of your deployments through the AWS Management Console or the AWS CLI

On the other hand, Terraform provides the following key features:

  • 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.

"Automates code deployments" is the primary reason why developers consider AWS CodeDeploy over the competitors, whereas "Infrastructure as code" was stated as the key factor in picking Terraform.

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.

Instacart, Slack, and Twitch are some of the popular companies that use Terraform, whereas AWS CodeDeploy is used by Adsia, Algorithmia, and indico. Terraform has a broader approval, being mentioned in 490 company stacks & 298 developers stacks; compared to AWS CodeDeploy, which is listed in 57 company stacks and 14 developer stacks.

Decisions about AWS CodeDeploy and Terraform

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 AWS CodeDeploy
Pros of Terraform
  • 17
    Automates code deployments
  • 9
    Backed by Amazon
  • 7
    Adds autoscaling lifecycle hooks
  • 5
    Git integration
  • 109
    Infrastructure as code
  • 72
    Declarative syntax
  • 44
    Planning
  • 27
    Simple
  • 24
    Parallelism
  • 7
    Cloud agnostic
  • 6
    Well-documented
  • 6
    It's like coding your infrastructure in simple English
  • 4
    Automates infrastructure deployments
  • 4
    Immutable infrastructure
  • 4
    Platform agnostic
  • 3
    Extendable
  • 3
    Automation
  • 3
    Portability
  • 2
    Lightweight
  • 2
    Scales to hundreds of hosts

Sign up to add or upvote prosMake informed product decisions

Cons of AWS CodeDeploy
Cons of Terraform
    Be the first to leave a con
    • 1
      Doesn't have full support to GKE

    Sign up to add or upvote consMake informed product decisions