AWS CodeDeploy vs. PDQ Deploy & Inventory

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

PDQ Inventory is great if you have a local network of computers on or off a domain. As long as you have a way to log into them with common credentials. Great for large organizations, particularly ones interconnected with VPNs. PDQ Inventory isn't so great for PCs that aren't connected to the same LAN the server is on. (i.e. non-vpn remote users) They used to have a remote agent you could install, but it was removed after numerous issues.

Incentivized

• Automate to deploy to AWS cloud environments
• Maximize application availability during product deployment
• AWS CodeDeploy provides CLI or web management console which can be viewed or edited at any environment

Incentivized

• Push out new software
• Push out Updates to current software
• Push out patches and updates that we don't have other ways to push out
• Keep end-users updated with little involvement

Incentivized

• When deploying a branch, sometimes the repository won't auto-populate, and you have to add the source manually

Incentivized

• As good as there email support is.. would like a live operator option
• Some updates are hard to understand when 5 versions of the same program exist
• Thats about it, PDQ deploy is the best out there

Incentivized

It is an easy and cost effective tool so it is an easy decision to renew.

Incentivized

The interface is straight forward and guides you through the process there. PDQ keeps track of the when new updates are made available writes the scripts and all l you need to do is push the button. (Mr George Jetson) Now with the download done you just sit back worry free and watch the software install in 1% of the time it would take to take care of the PC manually.

Incentivized

The built-in help menus and general ease of use render whatever systems support there might be almost irrelevant. There is stability in the system's simplicity; if you're in the position to use such a product, you're your own best friend. Simple web searches more often than not turn up the solution to any little niggles, such as what silent install switches specific applications require (a remarkably wide choice of options exist). System updates are timely and unobtrusive, installing in no time at all. Maybe I've just been lucky; if so, long may it continue!

Incentivized

Jenkins supports a lot of plugings. Also with Jenkins, it is possible to manage everything through our own server. Those are 2 points where I rate Jenkins as one of the best DevOps Tool

Incentivized

This software was referred to us by an IT professional. Previously, we were installing the software with the help of remote desktop applications but it was very time consuming; it was wasting the user's time since he could not use his computer. After testing PDQ Deploy, we just never looked back.

Incentivized

• 1-2 months per year of working time was saved from administration compared to on-prem legacy solution.
• Teams can trust more on the CI/CD pipeline and the deployments are faster, so the teams can deploy 10-15% more often compared to on-prem legacy solutions.
• Developers tend to desire more bells and whistles than CodeDeploy can offer, there has been some critique but this can be seen also as "editor war" (everyone has their opinion).

Incentivized

• Speed of deployment is very positive for new software setup, saving hours of testing and deployment locally
• Made patching for large computer estate very efficient, another positive for staff not having to spend hours of patching individual machines
• Works well for small team of IT's and again makes various repetitive tasks much easier

Incentivized