Concourse vs Varnish

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

Concourse

223
304
+ 1
48
Varnish

11.2K
1.7K
+ 1
358
Add tool

Concourse vs Varnish: What are the differences?

Concourse: Pipeline-based CI system written in Go. Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control; Varnish: High-performance HTTP accelerator. Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. Varnish Cache is really, really fast. It typically speeds up delivery with a factor of 300 - 1000x, depending on your architecture.

Concourse belongs to "Continuous Integration" category of the tech stack, while Varnish can be primarily classified under "Web Cache".

"Real pipelines" is the top reason why over 8 developers like Concourse, while over 99 developers mention "High-performance" as the leading cause for choosing Varnish.

Concourse and Varnish are both open source tools. Concourse with 4K GitHub stars and 482 forks on GitHub appears to be more popular than Varnish with 908 GitHub stars and 216 GitHub forks.

Pinterest, 9GAG, and Twitch are some of the popular companies that use Varnish, whereas Concourse is used by DigitalOcean, Starbucks, and HelloFresh. Varnish has a broader approval, being mentioned in 1006 company stacks & 140 developers stacks; compared to Concourse, which is listed in 18 company stacks and 17 developer stacks.

Advice on Concourse and Varnish
Needs advice
on
Jenkins
and
Concourse

I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

See more
Replies (1)
Maxi Krone
Cloud Engineer at fme AG · | 2 upvotes · 86.1K views
Recommends
Concourse

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Concourse
Pros of Varnish
  • 14
    Real pipelines
  • 9
    Containerised builds
  • 9
    Flexible engine
  • 5
    Fast
  • 3
    Open source
  • 3
    Simple configuration management
  • 3
    No Snowflakes
  • 1
    You have to do everything
  • 1
    Fancy Visualization
  • 102
    High-performance
  • 66
    Very Fast
  • 56
    Very Stable
  • 43
    Very Robust
  • 36
    HTTP reverse proxy
  • 20
    Open Source
  • 17
    Web application accelerator
  • 10
    Easy to config
  • 4
    Widely Used
  • 3
    Great community
  • 1
    Essential software for HTTP

Sign up to add or upvote prosMake informed product decisions

Cons of Concourse
Cons of Varnish
  • 2
    Fail forward instead of rollback pattern
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    What is Concourse?

    Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control.

    What is Varnish?

    Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. Varnish Cache is really, really fast. It typically speeds up delivery with a factor of 300 - 1000x, depending on your architecture.

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

    What companies use Concourse?
    What companies use Varnish?
    See which teams inside your own company are using Concourse or Varnish.
    Sign up for Private StackShareLearn More

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

    What tools integrate with Concourse?
    What tools integrate with Varnish?

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

    Blog Posts

    May 6 2020 at 6:34AM

    Pinterest

    +6
    3
    2060
    What are some alternatives to Concourse and Varnish?
    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.
    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.
    Spinnaker
    Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.
    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.
    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.
    See all alternatives