AWS CodeBuild聽vs聽Docker Compose

Get Advice Icon

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

AWS CodeBuild
AWS CodeBuild

98
54
+ 1
35
Docker Compose
Docker Compose

4.8K
3.3K
+ 1
446
Add tool

AWS CodeBuild vs Docker Compose: What are the differences?

What is AWS CodeBuild? Build and test code with continuous scaling. AWS CodeBuild is a fully managed build service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don鈥檛 need to provision, manage, and scale your own build servers.

What is Docker Compose? Define and run multi-container applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.

AWS CodeBuild belongs to "Continuous Integration" category of the tech stack, while Docker Compose can be primarily classified under "Container Tools".

"Pay per minute" is the primary reason why developers consider AWS CodeBuild over the competitors, whereas "Multi-container descriptor" was stated as the key factor in picking Docker Compose.

Docker Compose is an open source tool with 16.4K GitHub stars and 2.52K GitHub forks. Here's a link to Docker Compose's open source repository on GitHub.

StackShare, hike, and Harvest are some of the popular companies that use Docker Compose, whereas AWS CodeBuild is used by Convox, Volta Industries, and ChromaDex. Docker Compose has a broader approval, being mentioned in 787 company stacks & 608 developers stacks; compared to AWS CodeBuild, which is listed in 21 company stacks and 14 developer stacks.

- No public GitHub repository available -

What is AWS CodeBuild?

AWS CodeBuild is a fully managed build service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don鈥檛 need to provision, manage, and scale your own build servers.

What is Docker Compose?

With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.
Get Advice Icon

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

Why do developers choose AWS CodeBuild?
Why do developers choose Docker Compose?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use AWS CodeBuild?
    What companies use Docker Compose?

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

    What tools integrate with AWS CodeBuild?
    What tools integrate with Docker Compose?

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

    What are some alternatives to AWS CodeBuild and Docker Compose?
    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.
    AWS CodePipeline
    CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.
    Apache Maven
    Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.
    GitLab CI
    GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
    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.
    See all alternatives
    Decisions about AWS CodeBuild and Docker Compose
    Sebastian G臋bski
    Sebastian G臋bski
    CTO at Shedul/Fresha | 6 upvotes 41.6K views
    atFresha EngineeringFresha Engineering
    Amazon RDS
    Amazon RDS
    Amazon S3
    Amazon S3
    Amazon EKS
    Amazon EKS
    Amazon EC2
    Amazon EC2
    Ansible
    Ansible
    Terraform
    Terraform
    Kubernetes
    Kubernetes
    Docker Compose
    Docker Compose
    Docker
    Docker

    Heroku was a decent choice to start a business, but at some point our platform was too big, too complex & too heterogenic, so Heroku started to be a constraint, not a benefit. First, we've started containerizing our apps with Docker to eliminate "works in my machine" syndrome & uniformize the environment setup. The first orchestration was composed with Docker Compose , but at some point it made sense to move it to Kubernetes. Fortunately, we've made a very good technical decision when starting our work with containers - all the container configuration & provisions HAD (since the beginning) to be done in code (Infrastructure as Code) - we've used Terraform & Ansible for that (correspondingly). This general trend of containerisation was accompanied by another, parallel & equally big project: migrating environments from Heroku to AWS: using Amazon EC2 , Amazon EKS, Amazon S3 & Amazon RDS.

    See more
    GitHub
    GitHub
    nginx
    nginx
    ESLint
    ESLint
    AVA
    AVA
    Semantic UI React
    Semantic UI React
    Redux
    Redux
    React
    React
    PostgreSQL
    PostgreSQL
    ExpressJS
    ExpressJS
    Node.js
    Node.js
    FeathersJS
    FeathersJS
    Heroku
    Heroku
    Amazon EC2
    Amazon EC2
    Kubernetes
    Kubernetes
    Jenkins
    Jenkins
    Docker Compose
    Docker Compose
    Docker
    Docker
    #Frontend
    #Stack
    #Backend
    #Containers
    #Containerized

    Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

    We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

    See more
    Interest over time
    Reviews of AWS CodeBuild and Docker Compose
    Avatar of nzoschke
    Engineering Manager at Segment
    Review ofAWS CodeBuildAWS CodeBuild

    The open-source Convox Platform-as-a-Service is built entirely on AWS cloud services.

    Through this lens, it's been obvious that AWS has been missing a managed build service. For the past year we've had to work around this by building our own build service on ECS and ECR. You can read more on my AWS Missing Parts: Build Service blog post.

    So I'm excited to finally have this service. After a quick weekend prototype, the service works as expected and will unlock Cheaper, Faster and Safer Builds for our systems.

    This is a classic AWS service. It's tricky to figure out all the options. I recommend jumping straight to the Docker example docs:

    You'll need to figure IAM, Build Project JSON, and Build Spec YAML to get it all working.

    But once you do, you've unlocked managed builds on small, medium or large compute types. No instances required!

    How developers use AWS CodeBuild and Docker Compose
    Avatar of Chris Saylor
    Chris Saylor uses Docker ComposeDocker Compose

    Since our production deployment makes use of the Convox platform, we use this to describe the containers to be deployed via Convox to AWS ECS.

    We also use this for our local dev environment (previously used vagrant with chef).

    Avatar of Scrayos UG (haftungsbeschr盲nkt)
    Scrayos UG (haftungsbeschr盲nkt) uses Docker ComposeDocker Compose

    Aside from our Minecraft-infrastructure, we compose it with ... Docker Compose! (kinda obious, eh .. ?) This includes for example the web-services, aswell as the monitoring and mail-infrastructure.

    Avatar of sapslaj
    sapslaj uses Docker ComposeDocker Compose

    Docker Compose is just another part of my "infrastructure as code" initiative and allows me to build isolated pieces of systems with their own volumes and networks.

    Avatar of Sathish N
    Sathish N uses Docker ComposeDocker Compose

    Our application will consist of several containers each communicating with each other. Using docker-compose, we can orchestrate several containers at once.

    Avatar of Curabase
    Curabase uses Docker ComposeDocker Compose

    The core tech in ACS (Azure Container Services) we spin up a Kubernetes cluster and deploy our app into staging and production environments here.

    Avatar of Patty R
    Patty R uses AWS CodeBuildAWS CodeBuild

    build, test, deploys code

    How much does AWS CodeBuild cost?
    How much does Docker Compose cost?
    Pricing unavailable
    News about AWS CodeBuild
    More news