Alternatives to Beanstalk logo

Alternatives to Beanstalk

AWS Elastic Beanstalk, Heroku, Beanstalkd, Kubernetes, and GitHub are the most popular alternatives and competitors to Beanstalk.
86
220
+ 1
51

What is Beanstalk and what are its top alternatives?

A single process to commit code, review with the team, and deploy the final result to your customers.
Beanstalk is a tool in the Code Collaboration & Version Control category of a tech stack.

Top Alternatives to Beanstalk

  • AWS Elastic Beanstalk

    AWS Elastic Beanstalk

    Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring. ...

  • Heroku

    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

  • Beanstalkd

    Beanstalkd

    Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously. ...

  • Kubernetes

    Kubernetes

    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions. ...

  • GitHub

    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

  • GitLab

    GitLab

    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers. ...

  • Bitbucket

    Bitbucket

    Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users. ...

  • GitHub Enterprise

    GitHub Enterprise

    GitHub Enterprise lets developers use the tools they love across the development process with support for popular IDEs, continuous integration tools, and hundreds of third party apps and services. ...

Beanstalk alternatives & related posts

AWS Elastic Beanstalk logo

AWS Elastic Beanstalk

1.9K
1.6K
240
Quickly deploy and manage applications in the AWS cloud.
1.9K
1.6K
+ 1
240
PROS OF AWS ELASTIC BEANSTALK
  • 77
    Integrates with other aws services
  • 65
    Simple deployment
  • 44
    Fast
  • 28
    Painless
  • 16
    Free
  • 3
    Independend app container
  • 3
    Well-documented
  • 2
    Postgres hosting
  • 2
    Ability to be customized
CONS OF AWS ELASTIC BEANSTALK
  • 2
    Charges appear automatically after exceeding free quota
  • 0
    Slow deployments

related AWS Elastic Beanstalk posts

Julien DeFrance
Principal Software Engineer at Tophatter · | 16 upvotes · 2.3M views

Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

Future improvements / technology decisions included:

Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

See more

We initially started out with Heroku as our PaaS provider due to a desire to use it by our original developer for our Ruby on Rails application/website at the time. We were finding response times slow, it was painfully slow, sometimes taking 10 seconds to start loading the main page. Moving up to the next "compute" level was going to be very expensive.

We moved our site over to AWS Elastic Beanstalk , not only did response times on the site practically become instant, our cloud bill for the application was cut in half.

In database world we are currently using Amazon RDS for PostgreSQL also, we have both MariaDB and Microsoft SQL Server both hosted on Amazon RDS. The plan is to migrate to AWS Aurora Serverless for all 3 of those database systems.

Additional services we use for our public applications: AWS Lambda, Python, Redis, Memcached, AWS Elastic Load Balancing (ELB), Amazon Elasticsearch Service, Amazon ElastiCache

See more
Heroku logo

Heroku

18.3K
14K
3.2K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
18.3K
14K
+ 1
3.2K
PROS OF HEROKU
  • 702
    Easy deployment
  • 459
    Free for side projects
  • 374
    Huge time-saver
  • 348
    Simple scaling
  • 261
    Low devops skills required
  • 190
    Easy setup
  • 174
    Add-ons for almost everything
  • 154
    Beginner friendly
  • 150
    Better for startups
  • 133
    Low learning curve
  • 48
    Postgres hosting
  • 41
    Easy to add collaborators
  • 30
    Faster development
  • 24
    Awesome documentation
  • 19
    Simple rollback
  • 19
    Focus on product, not deployment
  • 15
    Natural companion for rails development
  • 15
    Easy integration
  • 12
    Great customer support
  • 8
    GitHub integration
  • 6
    Painless & well documented
  • 6
    No-ops
  • 4
    Free
  • 3
    I love that they make it free to launch a side project
  • 3
    Great UI
  • 3
    Just works
  • 2
    PostgreSQL forking and following
  • 2
    MySQL extension
CONS OF HEROKU
  • 23
    Super expensive
  • 6
    No usable MySQL option
  • 6
    Not a whole lot of flexibility
  • 5
    Storage
  • 4
    Low performance on free tier

related Heroku posts

Russel Werner
Lead Engineer at StackShare · | 29 upvotes · 1.4M views

StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 2.6M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Beanstalkd logo

Beanstalkd

104
127
74
A simple, fast work queue
104
127
+ 1
74
PROS OF BEANSTALKD
  • 23
    Fast
  • 12
    Free
  • 12
    Does one thing well
  • 9
    Scalability
  • 8
    Simplicity
  • 3
    External admin UI developer friendly
  • 3
    Job delay
  • 2
    Job prioritization
  • 2
    External admin UI
CONS OF BEANSTALKD
    Be the first to leave a con

    related Beanstalkd posts

    Frédéric MARAND
    Core Developer at OSInet · | 2 upvotes · 176.4K views

    I used Kafka originally because it was mandated as part of the top-level IT requirements at a Fortune 500 client. What I found was that it was orders of magnitude more complex ...and powerful than my daily Beanstalkd , and far more flexible, resilient, and manageable than RabbitMQ.

    So for any case where utmost flexibility and resilience are part of the deal, I would use Kafka again. But due to the complexities involved, for any time where this level of scalability is not required, I would probably just use Beanstalkd for its simplicity.

    I tend to find RabbitMQ to be in an uncomfortable middle place between these two extremities.

    See more
    Kubernetes logo

    Kubernetes

    33.9K
    28.4K
    601
    Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops
    33.9K
    28.4K
    + 1
    601
    PROS OF KUBERNETES
    • 152
      Leading docker container management solution
    • 121
      Simple and powerful
    • 96
      Open source
    • 73
      Backed by google
    • 56
      The right abstractions
    • 24
      Scale services
    • 17
      Replication controller
    • 9
      Permission managment
    • 6
      Simple
    • 5
      Supports autoscaling
    • 5
      Cheap
    • 3
      Reliable
    • 3
      No cloud platform lock-in
    • 3
      Self-healing
    • 3
      Open, powerful, stable
    • 3
      Scalable
    • 3
      Promotes modern/good infrascture practice
    • 2
      Cloud Agnostic
    • 2
      Backed by Red Hat
    • 2
      Custom and extensibility
    • 2
      Quick cloud setup
    • 2
      Captain of Container Ship
    • 2
      A self healing environment with rich metadata
    • 1
      Everything of CaaS
    • 1
      Easy setup
    • 1
      Expandable
    • 1
      Runs on azure
    • 1
      Sfg
    • 1
      Golang
    • 1
      Gke
    CONS OF KUBERNETES
    • 13
      Poor workflow for development
    • 11
      Steep learning curve
    • 5
      Orchestrates only infrastructure
    • 2
      High resource requirements for on-prem clusters

    related Kubernetes posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 38 upvotes · 3.7M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Yshay Yaacobi

    Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

    Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

    After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

    See more
    GitHub logo

    GitHub

    165.2K
    132.4K
    10.2K
    Powerful collaboration, review, and code management for open source and private development projects
    165.2K
    132.4K
    + 1
    10.2K
    PROS OF GITHUB
    • 1.8K
      Open source friendly
    • 1.5K
      Easy source control
    • 1.2K
      Nice UI
    • 1.1K
      Great for team collaboration
    • 857
      Easy setup
    • 496
      Issue tracker
    • 478
      Great community
    • 475
      Remote team collaboration
    • 444
      Great way to share
    • 436
      Pull request and features planning
    • 139
      Just works
    • 125
      Integrated in many tools
    • 112
      Free Public Repos
    • 106
      Github Gists
    • 103
      Github pages
    • 81
      Easy to find repos
    • 60
      Open source
    • 58
      Easy to find projects
    • 56
      Network effect
    • 55
      It's free
    • 47
      Extensive API
    • 42
      Organizations
    • 41
      Branching
    • 33
      Developer Profiles
    • 32
      Git Powered Wikis
    • 29
      Great for collaboration
    • 23
      It's fun
    • 22
      Community SDK involvement
    • 21
      Clean interface and good integrations
    • 19
      Learn from others source code
    • 14
      It integrates directly with Azure
    • 14
      Because: Git
    • 13
      Wide acceptance
    • 10
      Large community
    • 9
      Newsfeed
    • 9
      Standard in Open Source collab
    • 8
      It integrates directly with Hipchat
    • 7
      Beautiful user experience
    • 7
      Fast
    • 6
      Easy to discover new code libraries
    • 6
      Cloud SCM
    • 5
      Graphs
    • 5
      Smooth integration
    • 5
      Nice API
    • 5
      Integrations
    • 5
      It's awesome
    • 4
      Remarkable uptime
    • 4
      Hands down best online Git service available
    • 4
      Reliable
    • 3
      Easy to use and collaborate with others
    • 3
      CI Integration
    • 3
      Free HTML hosting
    • 3
      Loved by developers
    • 3
      Quick Onboarding
    • 3
      Security options
    • 3
      Simple but powerful
    • 3
      Uses GIT
    • 3
      Unlimited Public Repos at no cost
    • 3
      Version Control
    • 2
      Nice to use
    • 1
      Free private repos
    • 1
      Easy deployment via SSH
    • 1
      Beautiful
    • 1
      Owned by micrcosoft
    • 1
      Free HTML hostings
    • 1
      Self Hosted
    • 1
      All in one development service
    • 1
      Easy to use
    • 1
      Good tools support
    • 1
      Easy source control and everything is backed up
    • 1
      Leads the copycats
    • 1
      Never dethroned
    • 1
      Ci
    • 1
      Issues tracker
    • 1
      Easy and efficient maintainance of the projects
    • 1
      IAM
    • 1
      IAM integration
    • 0
      Profound
    • 0
      1
    CONS OF GITHUB
    • 45
      Owned by micrcosoft
    • 36
      Expensive for lone developers that want private repos
    • 15
      Relatively slow product/feature release cadence
    • 10
      API scoping could be better
    • 8
      Only 3 collaborators for private repos
    • 3
      Limited featureset for issue management
    • 2
      GitHub Packages does not support SNAPSHOT versions
    • 1
      Have to use a token for the package registry
    • 1
      No multilingual interface
    • 1
      Takes a long time to commit

    related GitHub posts

    Johnny Bell
    Software Engineer at Weedmaps · | 77 upvotes · 1.1M views

    I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

    I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

    I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

    Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

    Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

    With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

    If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

    See more
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 2.6M views

    Our whole DevOps stack consists of the following tools:

    • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
    • Respectively Git as revision control system
    • SourceTree as Git GUI
    • Visual Studio Code as IDE
    • CircleCI for continuous integration (automatize development process)
    • Prettier / TSLint / ESLint as code linter
    • SonarQube as quality gate
    • Docker as container management (incl. Docker Compose for multi-container application management)
    • VirtualBox for operating system simulation tests
    • Kubernetes as cluster management for docker containers
    • Heroku for deploying in test environments
    • nginx as web server (preferably used as facade server in production environment)
    • SSLMate (using OpenSSL) for certificate management
    • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
    • PostgreSQL as preferred database system
    • Redis as preferred in-memory database/store (great for caching)

    The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

    • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
    • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
    • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
    • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
    • Scalability: All-in-one framework for distributed systems.
    • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
    See more
    GitLab logo

    GitLab

    37.5K
    30.1K
    2.3K
    Open source self-hosted Git management software
    37.5K
    30.1K
    + 1
    2.3K
    PROS OF GITLAB
    • 489
      Self hosted
    • 418
      Free
    • 332
      Has community edition
    • 236
      Easy setup
    • 235
      Familiar interface
    • 130
      Includes many features, including ci
    • 106
      Nice UI
    • 80
      Good integration with gitlabci
    • 52
      Simple setup
    • 32
      Has an official mobile app
    • 30
      Free private repository
    • 24
      Continuous Integration
    • 16
      Open source, great ui (like github)
    • 14
      Slack Integration
    • 9
      Full CI flow
    • 8
      User, group, and project access management is simple
    • 8
      Free and unlimited private git repos
    • 7
      Intuitive UI
    • 7
      All in one (Git, CI, Agile..)
    • 6
      Built-in CI
    • 4
      Both public and private Repositories
    • 3
      Mattermost Chat client
    • 3
      Integrated Docker Registry
    • 2
      It's fully integrated
    • 2
      Unlimited free repos & collaborators
    • 2
      I like the its runners and executors feature
    • 2
      CI
    • 2
      So easy to use
    • 2
      One-click install through DigitalOcean
    • 2
      It's powerful source code management tool
    • 2
      Excellent
    • 2
      Build/pipeline definition alongside code
    • 2
      Security and Stable
    • 2
      Issue system
    • 2
      Free private repos
    • 2
      Low maintenance cost due omnibus-deployment
    • 2
      On-premises
    • 1
      Powerful Continuous Integration System
    • 1
      Powerful software planning and maintaining tools
    • 1
      Groups of groups
    • 1
      Kubernetes integration with GitLab CI
    • 1
      Review Apps feature
    • 1
      Built-in Docker Registry
    • 1
      Dockerized
    • 1
      Beautiful
    • 1
      Wounderful
    • 1
      Opensource
    • 1
      Because is the best remote host for git repositories
    • 1
      Not Microsoft Owned
    • 1
      Full DevOps suite with Git
    • 1
      Many private repo
    • 1
      Native CI
    • 1
      HipChat intergration
    • 1
      Kubernetes Integration
    • 1
      Published IP list for whitelisting (gl-infra#434)
    • 1
      Great for team collaboration
    • 1
      It includes everything I need, all packaged with docker
    • 1
      Multilingual interface
    • 1
      The dashboard with deployed environments
    • 0
      Supports Radius/Ldap & Browser Code Edits
    CONS OF GITLAB
    • 26
      Slow ui performance
    • 6
      Introduce breaking bugs every release
    • 5
      Insecure (no published IP list for whitelisting)
    • 0
      Built-in Docker Registry
    • 0
      Review Apps feature

    related GitLab posts

    Tim Abbott
    Shared insights
    on
    GitHub
    GitLab
    at

    I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.

    But even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:

    • You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).
    • You can't let anyone with a GitHub account self-assign issues to themselves.
    • Many more similar issues.

    It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab.

    We have a custom bot project, http://github.com/zulip/zulipbot, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less.

    See more
    Joshua Dean Küpper
    CEO at Scrayos UG (haftungsbeschränkt) · | 17 upvotes · 224.4K views

    We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

    While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

    We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

    See more
    Bitbucket logo

    Bitbucket

    29.4K
    22.6K
    2.8K
    One place to plan projects, collaborate on code, test and deploy, all with free private repositories
    29.4K
    22.6K
    + 1
    2.8K
    PROS OF BITBUCKET
    • 904
      Free private repos
    • 397
      Simple setup
    • 345
      Nice ui and tools
    • 340
      Unlimited private repositories
    • 239
      Affordable git hosting
    • 122
      Integrates with many apis and services
    • 118
      Reliable uptime
    • 85
      Nice gui
    • 83
      Pull requests and code reviews
    • 57
      Very customisable
    • 15
      Mercurial repositories
    • 13
      SourceTree integration
    • 10
      JIRA integration
    • 9
      Track every commit to an issue in JIRA
    • 7
      Best free alternative to Github
    • 7
      Automatically share repositories with all your teammates
    • 7
      Deployment hooks
    • 6
      Compatible with Mac and Windows
    • 5
      Source Code Insight
    • 4
      Price
    • 4
      Login with Google
    • 4
      Create a wiki
    • 4
      Approve pull request button
    • 3
      #2 Atlassian Product after JIRA
    • 3
      Customizable pipelines
    • 2
      Also supports Mercurial
    • 2
      Unlimited Private Repos at no cost
    • 2
      Continuous Integration and Delivery
    • 1
      Mercurial Support
    • 1
      IAM
    • 1
      Issues tracker
    • 1
      Open source friendly
    • 1
      Teamcity
    • 1
      Multilingual interface
    • 1
      Academic license program
    • 1
      IAM integration
    • 0
      Free Private Repositories
    CONS OF BITBUCKET
    • 19
      Not much community activity
    • 17
      Difficult to review prs because of confusing ui
    • 14
      Quite buggy
    • 10
      Managed by enterprise Java company
    • 8
      CI tool is not free of charge
    • 7
      Complexity with rights management
    • 6
      Only 5 collaborators for private repos
    • 4
      Slow performance
    • 2
      No AWS Codepipelines integration
    • 1
      No more Mercurial repositories
    • 1
      No server side git-hook support

    related Bitbucket posts

    Michael Kelly
    Senior Software Engineer at StackShare · | 14 upvotes · 587.5K views

    I use GitLab when building side-projects and MVPs. The interface and interactions are close enough to those of GitHub to prevent cognitive switching costs between professional and personal projects hosted on different services.

    GitLab also provides a suite of tools including issue/project management, CI/CD with GitLab CI, and validation/landing pages with GitLab Pages. With everything in one place, on an #OpenSourceCloud GitLab makes it easy for me to manage much larger projects on my own, than would be possible with other solutions or tools.

    It's petty I know, but I can also read the GitLab code diffs far more easily than diffs on GitHub or Bitbucket...they just look better in my opinion.

    See more
    Shared insights
    on
    GitHub
    GitLab
    Bitbucket

    A bit difference in GitHub and GitLab though both are Version Control repository management services which provides key component in the software development workflow. A decision of choosing GitHub over GitLab is major leap extension from code management, to deployment and monitoring alongside looking beyond the code base hosting provided best fitted tools for developer communities.

    • Authentication stages - With GitLab you can set and modify people’s permissions according to their role. In GitHub, you can decide if someone gets a read or write access to a repository.
    • Built-In Continuous Integrations - GitLab offers its very own CI for free. No need to use an external CI service. And if you are already used to an external CI, you can obviously integrate with Jenkins, etc whereas GitHub offers various 3rd party integrations – such as Travis CI, CircleCI or Codeship – for running and testing your code. However, there’s no built-in CI solution at the moment.
    • Import/Export Resources - GitLab offers detailed documentation on how to import your data from other vendors – such as GitHub, Bitbucket to GitLab. GitHub, on the other hand, does not offer such detailed documentation for the most common git repositories. However, GitHub offers to use GitHub Importer if you have your source code in Subversion, Mercurial, TFS and others.

    Also when it comes to exporting data, GitLab seems to do a pretty solid job, offering you the ability to export your projects including the following data:

    • Wiki and project repositories
    • Project uploads
    • The configuration including webhooks and services
    • Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities.

    GitHub, on the other hand, seems to be more restrictive when it comes to export features of existing GitHub repositories. * Integrations - #githubmarketplace gives you an essence to have multiple and competitive integrations whereas you will find less in the GitLab.

    So go ahead with better understanding.

    See more
    GitHub Enterprise logo

    GitHub Enterprise

    484
    525
    6
    The on-premises version of GitHub, which you can deploy and manage in your own, secure environment
    484
    525
    + 1
    6
    PROS OF GITHUB ENTERPRISE
    • 2
      Expensive - $$$
    • 1
      Both Cloud and Enterprise Server Versions available
    • 1
      CDCI with Github Actions
    • 1
      Code security
    • 1
      Draft Pull Request
    CONS OF GITHUB ENTERPRISE
    • 1
      $$$

    related GitHub Enterprise posts

    Eric Seibert
    DevOps at Children's Hospital of Philadelphia · | 6 upvotes · 60.6K views

    We are using a Bitbucket server, and due to migration efforts and new Atlassian community license changes, we need to move to a new self-hosted solution. The new data-center license for Atlassian, available in February, will be community provisioned (free). Along with that community license, other technologies will be coming with it (Crucible, Confluence, and Jira). Is there value in a paid-for license to get the GitHub Enterprise? Are the tools that come with it worth the cost?

    I know it is about $20 per 10 seats, and we have about 300 users. Have other convertees to Microsoft's tools found it easy to do a migration? Is the toolset that much more beneficial to the free suite that one can get from Atlassian?

    So far, free seems to be the winner, and the familiarization with Atlassian implementation and maintenance is understood. Going to GitHub, are there any distinct challenges to be found or any perks to be attained?

    See more