AWS Batch vs. AWS CodePipeline

More appropriate if you have a tech group that can use more of the AWS Batch rather than one or 2 things. It works great for me, but there was a huge learning curve the first week of using it. Now, I love it - and I hope to dig deep into other parts not just S3.

Incentivized

I think AWS CodePipeline is a great tool for anyone wanted automated deployments in a multi-server/container AWS environment. AWS also offers services like Elastic Beanstalk that provide a more managed hosting & deployment experience. CodePipeline is a good middle ground with solid, built-in automation with enough customizability to not lock people into one deployment or architecture philosophy.

Incentivized

• Easy to orchestrate and trigger jobs
• No time limit issues like lambda
• Multiple Jobs can be run in same single compute and job queue
• JOb queue can queue up task for parralled or serialization

Incentivized

• It is reliable and works without errors
• It integrates well with our repository and all other AWS functions as well as our end database

Incentivized

• Jobs monitoring dashboards are not matured
• Documentation and support is something which can be improved
• Sometime i faced the slow response or slow in performance i would say

Incentivized

• Ease of use - things like CircleCI or other tools are a bit easier to learn.
• Ability to build from more sources.

Incentivized

Key advantages include cost-effectiveness through dynamic resource provisioning and the use of spot instances. It auto-scales to meet workload demands, allowing easy job submission via the AWS Management Console or SDKs. It integrates seamlessly with other services like S3 and CloudWatch. It features automatic retries for failed jobs. It allows for a custom computing environment tailored to specific needs

Incentivized

Overall, I give AWS Codepipeline a 9 because it gets the job done and I can't complain much about the web interface as much of the action is taking place behind the scenes on the terminal locally or via Amazon's infrastructure anyway. It would be nicer to have a better flowing and visualizable web interface, however.

Incentivized

Our pipeline takes about 30 minutes to run through. Although this time depends on the applications you are using on either end, I feel that it is a reasonable time to make upgrades and updates to our system as it is not an every day push.

Incentivized

We didn't need a lot of support with AWS CodePipeline as it was pretty straightforward to configure and use, but where we ran into problems, the AWS community was able to help. AWS support agents were also helpful in resolving some of the minor issues we encountered, which we could not find a solution elsewhere.

Incentivized

We wanted to start everything on a scale & with fewer resources to manage the underlying infrastructure.

Incentivized

CodeCommit and CodeDeploy can be used with CodePipeline so it’s not really fair to stack them against each other as they can be quite the compliment. The same goes for Beanstalk, which is often used as a deployment target in relation to CodePipeline.

CodePipeline fulfills the CI/CD duty, where the other services do not focus on that specific function. They are supplements, not replacements. CodePipeline will detect the updated code and handle deploying it to the actual instance via Beanstalk.

Jenkins is open source and not a native AWS service, that is its primary differentiator. Jenkins can also be used as a supplement to CodePipeline.

Incentivized

• Overall over business is able to save the cost
• Saved our times to improve the existing process
• Able to integrate with other applications as well, so that is plus point

Incentivized

• CodePipeline has reduced ongoing devops costs for my clients, especially around deployment & testing.
• CodePipeline has sped up development workflow by making the deployment process automated off git pushes. Deployment takes very little coordination as the system will just trigger based on what is the latest commit in a branch.
• CodePipeline offered a lot of out-of-the-box functionality that was much simpler to setup than a dedicated CI server. It allowed the deployment process to built and put into production with much less and effort and cost compared to rolling the functionality manually.

Incentivized