AWS Elastic Load Balancing (ELB) vs Jenkins

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

AWS Elastic Load Balancing (ELB)

12.5K
8.6K
+ 1
59
Jenkins

57.8K
49.3K
+ 1
2.2K
Add tool

AWS Elastic Load Balancing (ELB) vs Jenkins: What are the differences?

AWS Elastic Load Balancing (ELB) vs Jenkins

Introduction:

AWS Elastic Load Balancing (ELB) and Jenkins are both popular tools used in website development and deployment. While ELB is a service provided by Amazon Web Services (AWS) for distributing incoming application traffic across multiple targets, Jenkins is an open-source automation server used for continuous integration and delivery of software projects.

1. Scalability and Availability: ELB is designed to automatically distribute incoming traffic across multiple instances, helping to achieve high availability of applications. It can seamlessly scale with the increase in traffic and can handle traffic spikes efficiently. On the other hand, Jenkins focuses on automating the development and deployment process rather than directly managing the scalability and availability aspects.

2. Traffic Routing and Load Distribution: ELB provides advanced traffic routing capabilities, allowing users to configure rules based on various parameters like path patterns, host headers, and query strings. It supports different load balancing algorithms to evenly distribute traffic across instances. Jenkins, on the other hand, primarily focuses on automating the build, test, and deployment process and does not provide built-in traffic routing or load balancing capabilities.

3. Deployment and Infrastructure Management: ELB simplifies the deployment process by automatically distributing traffic across multiple instances, making it easy to manage and monitor applications. It integrates well with other AWS services like Auto Scaling and CloudWatch, providing a comprehensive infrastructure management solution. In contrast, Jenkins is primarily focused on automation and does not offer the same level of infrastructure management capabilities as ELB.

4. User Interface and Usability: ELB provides a user-friendly web interface as part of the AWS Management Console, making it easy for users to configure and manage load balancers. It offers a simple and intuitive interface for setting up routing rules, monitoring traffic, and managing instances. Jenkins, on the other hand, is a self-hosted automation server that provides a web-based UI for managing Jenkins jobs and configurations. While Jenkins offers flexibility and customization options, it may require more technical expertise to set up and configure compared to ELB.

5. Cost and Pricing Model: ELB is billed based on the amount of data processed and the number of load balancer hours used. The pricing is flexible and varies based on factors like the number of instances, traffic volume, and data transfer. On the other hand, Jenkins is an open-source tool, and the cost is mainly associated with the infrastructure required to host the Jenkins server and the resources utilized for running jobs. Jenkins can be run on self-hosted servers or cloud platforms, providing flexibility in terms of cost management.

6. Integration and Extensibility: ELB integrates seamlessly with other AWS services like Auto Scaling, AWS Certificate Manager, and AWS Identity and Access Management (IAM), providing a holistic solution for managing and scaling applications. It also offers APIs and SDKs for programmatic access and extensibility. Jenkins, being an open-source project, has a wide range of plugins and integrations available for various tools and technologies, making it highly customizable and extensible.

In summary, AWS Elastic Load Balancing (ELB) provides scalable and highly available load balancing and routing capabilities with a comprehensive infrastructure management solution, while Jenkins is focused on automating the development and deployment process through continuous integration and delivery. ELB offers advanced traffic routing, scalability, and integration with other AWS services, while Jenkins provides flexibility, customization, and extensibility through plugins and extensive community support.

Advice on AWS Elastic Load Balancing (ELB) and Jenkins
Needs advice
on
Azure PipelinesAzure Pipelines
and
JenkinsJenkins

We are currently using Azure Pipelines for continous integration. Our applications are developed witn .NET framework. But when we look at the online Jenkins is the most widely used tool for continous integration. Can you please give me the advice which one is best to use for my case Azure pipeline or jenkins.

See more
Replies (1)
Recommends
on
GitHubGitHub

If your source code is on GitHub, also take a look at Github actions. https://github.com/features/actions

See more
Mohammad Hossein Amri
Chief Technology Officer at Planally · | 3 upvotes · 504.9K views
Needs advice
on
GoCDGoCD
and
JenkinsJenkins

I'm open to anything. just want something that break less and doesn't need me to pay for it, and can be hosted on Docker. our scripting language is powershell core. so it's better to support it. also we are building dotnet core in our pipeline, so if they have anything related that helps with the CI would be nice.

See more
Replies (1)
Ankit Malik
Software Developer at CloudCover · | 1 upvotes · 487.6K views
Recommends
on
Google Cloud BuildGoogle Cloud Build

Google cloud build can help you. It is hosted on cloud and also provide reasonable free quota.

See more
Needs advice
on
ConcourseConcourse
and
JenkinsJenkins

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 · 406.5K views
Recommends
on
ConcourseConcourse

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
Needs advice
on
JenkinsJenkinsTravis CITravis CI
and
CircleCICircleCI

From a StackShare Community member: "Currently we use Travis CI and have optimized it as much as we can so our builds are fairly quick. Our boss is all about redundancy so we are looking for another solution to fall back on in case Travis goes down and/or jacks prices way up (they were recently acquired). Could someone recommend which CI we should go with and if they have time, an explanation of how they're different?"

See more
Replies (6)
Dustin Falgout
Senior Developer at Elegant Themes · | 13 upvotes · 559.3K views

We use CircleCI because of the better value it provides in its plans. I'm sure we could have used Travis just as easily but we found CircleCI's pricing to be more reasonable. In the two years since we signed up, the service has improved. CircleCI is always innovating and iterating on their platform. We have been very satisfied.

See more
Peter Thomas
Distinguished Engineer at Intuit · | 9 upvotes · 870.3K views
Recommends
on
Travis CITravis CI
at

As the maintainer of the Karate DSL open-source project - I found Travis CI very easy to integrate into the GitHub workflow and it has been steady sailing for more than 2 years now ! It works well for Java / Apache Maven projects and we were able to configure it to use the latest Oracle JDK as per our needs. Thanks to the Travis CI team for this service to the open-source community !

See more
Recommends
on
Google Cloud BuildGoogle Cloud Build

I use Google Cloud Build because it's my first foray into the CICD world(loving it so far), and I wanted to work with something GCP native to avoid giving permissions to other SaaS tools like CircleCI and Travis CI.

I really like it because it's free for the first 120 minutes, and it's one of the few CICD tools that enterprises are open to using since it's contained within GCP.

One of the unique things is that it has the Kaniko cache, which speeds up builds by creating intermediate layers within the docker image vs. pushing the full thing from the start. Helpful when you're installing just a few additional dependencies.

Feel free to checkout an example: Cloudbuild Example

See more
Recommends
on
Travis CITravis CI

I use Travis CI because of various reasons - 1. Cloud based system so no dedicated server required, and you do not need to administrate it. 2. Easy YAML configuration. 3. Supports Major Programming Languages. 4. Support of build matrix 6. Supports AWS, Azure, Docker, Heroku, Google Cloud, Github Pages, PyPi and lot more. 7. Slack Notifications.

See more
Oded Arbel
Recommends
on
GitLab CIGitLab CI

You are probably looking at another hosted solution: Jenkins is a good tool but it way too work intensive to be used as just a backup solution.

I have good experience with Circle-CI, Codeship, Drone.io and Travis (as well as problematic experiences with all of them), but my go-to tool is Gitlab CI: simple, powerful and if you have problems with their limitations or pricing, you can always install runners somewhere and use Gitlab just for scheduling and management. Even if you don't host your git repository at Gitlab, you can have Gitlab pull changes automatically from wherever you repo lives.

See more
Recommends
on
BuildkiteBuildkite

If you are considering Jenkins I would recommend at least checking out Buildkite. The agents are self-hosted (like Jenkins) but the interface is hosted for you. It meshes up some of the things I like about hosted services (pipeline definitions in YAML, managed interface and authentication) with things I like about Jenkins (local customizable agent images, secrets only on own instances, custom agent level scripts, sizing instances to your needs).

See more
Decisions about AWS Elastic Load Balancing (ELB) and Jenkins

Jenkins is a pretty flexible, complete tool. Especially I love the possibility to configure jobs as a code with Jenkins pipelines.

CircleCI is well suited for small projects where the main task is to run continuous integration as quickly as possible. Travis CI is recommended primarily for open-source projects that need to be tested in different environments.

And for something a bit larger I prefer to use Jenkins because it is possible to make serious system configuration thereby different plugins. In Jenkins, I can change almost anything. But if you want to start the CI chain as soon as possible, Jenkins may not be the right choice.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of AWS Elastic Load Balancing (ELB)
Pros of Jenkins
  • 48
    Easy
  • 8
    ASG integration
  • 2
    Reliability
  • 1
    Coding
  • 0
    SSL offloading
  • 523
    Hosted internally
  • 469
    Free open source
  • 318
    Great to build, deploy or launch anything async
  • 243
    Tons of integrations
  • 211
    Rich set of plugins with good documentation
  • 111
    Has support for build pipelines
  • 68
    Easy setup
  • 66
    It is open-source
  • 53
    Workflow plugin
  • 13
    Configuration as code
  • 12
    Very powerful tool
  • 11
    Many Plugins
  • 10
    Continuous Integration
  • 10
    Great flexibility
  • 9
    Git and Maven integration is better
  • 8
    100% free and open source
  • 7
    Slack Integration (plugin)
  • 7
    Github integration
  • 6
    Self-hosted GitLab Integration (plugin)
  • 6
    Easy customisation
  • 5
    Pipeline API
  • 5
    Docker support
  • 4
    Fast builds
  • 4
    Hosted Externally
  • 4
    Excellent docker integration
  • 4
    Platform idnependency
  • 3
    AWS Integration
  • 3
    JOBDSL
  • 3
    It's Everywhere
  • 3
    Customizable
  • 3
    Can be run as a Docker container
  • 3
    It`w worked
  • 2
    Loose Coupling
  • 2
    NodeJS Support
  • 2
    Build PR Branch Only
  • 2
    Easily extendable with seamless integration
  • 2
    PHP Support
  • 2
    Ruby/Rails Support
  • 2
    Universal controller

Sign up to add or upvote prosMake informed product decisions

Cons of AWS Elastic Load Balancing (ELB)
Cons of Jenkins
    Be the first to leave a con
    • 13
      Workarounds needed for basic requirements
    • 10
      Groovy with cumbersome syntax
    • 8
      Plugins compatibility issues
    • 7
      Lack of support
    • 7
      Limited abilities with declarative pipelines
    • 5
      No YAML syntax
    • 4
      Too tied to plugins versions

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is AWS Elastic Load Balancing (ELB)?

    With Elastic Load Balancing, you can add and remove EC2 instances as your needs change without disrupting the overall flow of information. If one EC2 instance fails, Elastic Load Balancing automatically reroutes the traffic to the remaining running EC2 instances. If the failed EC2 instance is restored, Elastic Load Balancing restores the traffic to that instance. Elastic Load Balancing offers clients a single point of contact, and it can also serve as the first line of defense against attacks on your network. You can offload the work of encryption and decryption to Elastic Load Balancing, so your servers can focus on their main task.

    What is 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.

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

    What companies use AWS Elastic Load Balancing (ELB)?
    What companies use Jenkins?
    See which teams inside your own company are using AWS Elastic Load Balancing (ELB) or Jenkins.
    Sign up for StackShare EnterpriseLearn More

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

    What tools integrate with AWS Elastic Load Balancing (ELB)?
    What tools integrate with Jenkins?

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

    Blog Posts

    Mar 24 2021 at 12:57PM

    Pinterest

    GitJenkinsKafka+7
    3
    2159
    GitJenkinsGroovy+4
    4
    2687
    Dec 4 2019 at 8:01PM

    Pinterest

    KubernetesJenkinsTensorFlow+4
    5
    3288
    JavaScriptGitHubNode.js+29
    14
    13479
    GitHubPythonReact+42
    49
    40783
    What are some alternatives to AWS Elastic Load Balancing (ELB) and Jenkins?
    JavaScript
    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
    Git
    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
    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.
    Python
    Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best.
    jQuery
    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML.
    See all alternatives