AWS CodeDeploy is a fully managed deployment service that automates software deployments to a variety of compute services such as Amazon EC2, AWS Fargate, AWS Lambda, and on-premises servers. AWS CodeDeploy aims to make it easier for users to rapidly release new features, avoid downtime during application deployment, and handle the complexity of updating applications.
$0.02
per on-premises instance
Microsoft System Center
Score 8.2 out of 10
N/A
Microsoft System Center Suite is a family of IT management software for network monitoring, updating and patching, endpoint protection with anti-malware, data protection and backup, ITIL- structured IT service management, remote administration and more.
It is available in two editions: standard and datacenter. Datacenter provides unlimited virtualization for high density private clouds, while standard is for lightly or non-virtualized private cloud workloads.
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.
We used a product before that was designed to prevent users making changes and saving files to the desktop computer. This required a renewal of the license. By using SCCM in our environment we were able to discontinue using that product because SCCM allows us to completely restore a machine back to the original configuration. We have taught our users to save their individual work on either a network drive or a cloud drive. By doing this, if we do a re-image of their machine they have lost no data, and it makes for a faster resolution. In some instances having a computer in our SCCM environment it can become cumbersome when creating new users for very specific purposes. It can be done by creating new organizational units and applying new policies but when in a pinch it can be frustrating. For the most part we have tried to make "new" purpose images and groups to at least accommodate a quick install.
Provides our users the ability to deploy and manage our own datacenter based on defined software with understandable solutions for storage, compute, networking and security.
We are able to update at once all the computers from all departments without having to install the OS on every computer.
It allows us to have everything in one place for database management and datacenter inspection as well.
Needs web based storefront for requesting new software
Needs ability to manage the packaging work flow better
Sometimes is slow to download and there is no indication the entire catalog is being loaded, resulting in confused users not being able to find common software in the available list.
It is not user-friendly for the most part. With IT infrastructure, sometimes it cannot handle excess requests. Every few months, you will need an upgrade in terms of server resources to keep up with incoming alerts and requests. This does not happen all of the time, but it does happen when there are too many requests.
If I had to dislike something about the system it would be how much it changes once you upgrade. This could be more of a problem of mine since I get used to one way and don't like it when it changes so much. I am enjoying the newest update, but it is a mess when you are actually going through the upgrades.
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
We previously used a mix of FOG and Clonezilla to image machines. The biggest issues with these products is that changing one piece of the image required you to rebuild the entire image itself. These pieces of software also did not allow you to manage applications and Windows Updates, causing IT to have to constantly touch machines after they were imaged and update or manage them with a much more hands on approach.
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).
We have been able to automate our patch management, firmware and other security concerns.
We have a standardized "image" ensuring our setup is consistent across the enterprise. This alone has saved us in time to support and time to understand how to use our desktops.
