AWS CodeDeploy vs. Homebrew

For greenfield projects built on AWS there are very few reasons why not to choose AWS CodeDeploy. It works out of the box and integrates seamlessly into your cloud environment. If you plan to migrate your existing legacy builds away e.g. from Jenkins, you may need to reserve a substantial amount of time for that and the benefits gained may not be worth the effort.

Incentivized

• Simplifies checking the status of code branches
• Streamlines the deployment process
• Integrates into our Slack workflow for reserving environments

Incentivized

• Would Love to have more traceability when troubleshooting

Incentivized

Here is where AWS as a whole stepped up big. The UI is more intuitive and easy to use. The separation is clear, and the guides are abundant. They still need to create starter tutorials for newcomers so we don't lose much time learning/teaching others. Having someone with basic knowledge and examples where they can gain experience will make it better.

Incentivized

Both have the same concept, but AWS has gained some ground over Google by creating cheaper services, and the fact they have servers wherever there is an Amazon makes the speed to access the platform faster and the jumps in the network also quicker. GCP has its global advantage because it is extremely easy to use, but overall, AWS has more to offer as long as you know it.

Incentivized

• Definite positive impact
• This tool provides automate features which reduce the dev ops work load
• This tool works in many different languages so we can have a generic setup code for different languages
• No negative impact

Incentivized