Chef Reviews

We use it for integration management.

The community.

The agent on the server sometimes acts finicky. 

It is stable most of the time. There hasn't been any downtime.

We did not go with the traditional architecture, so we decided to use the AWS systems by decoupling the traditional architecture.

The scalability of the product is quite nice. We have deployed it across six to seven organizations.

The technical support is very good.

The integration and configuration in our AWS environment is very good.

It works well with most operation management systems, and where it doesn't, we upgrade the system.

We have seen ROI.

We tried Ansible and Jenkins. However, because we use Terraform in our products, these weren't the most fitting solutions. Chef was the best solution for helping us build our infrastructure.

Find use cases and do your research.

We only use the AWS version. We tried the other versions, but we found that they were lacking in functionality.

I have used in my current company for three years, and with other clients for more than ten years.

My clients are happy, which is the most important thing.

The most valuable feature is automation. 

The AWS monitoring, AWS X-Ray, and some other features could be improved.

We have some issues in Brazilian region with stability. However, in US region, we have no issues with stability.

Scalability is pretty good. We have nothing to complain about, except the price.

I would rate the technical support as a ten out of ten.

Amazon is a great partner.

The integration and configuration are pretty good in the AWS environment. The problems are usually on our side, not on AWS' side.

The price is always a problem. It is high. There is room for improvement. I do like purchasing on the AWS Marketplace, but I would like the ability to negotiate and have some flexibility in the pricing on it. 

I don't like some of the products offered by VMware. I like the automation offered by Chef and Puppet.

We chose Chef because some clients have some legacy systems and decided to work with them. We don't really like work with VMs, but when we have to, we use Puppet.

I have used the on-premise and AWS versions. I prefer the AWS for troubleshooting.

It integrates with many products in ILT, data management, and the server areas with each of them providing cloud computing, like EC2 and API Gateway.

We use it for training.

All the Chef enthusiasts who come to us to learn and train, improve their skillsets to get jobs. It's a really easy product in AWS. It's easy to teach and easy to understand.

The most valuable feature is the language that it uses: Ruby.

Regarding integration and configuration of the product, they're pretty manageable. The layers are really easy to configure.

I would like to see more security features for Chef and more automation.

It's working great. It's stable. We try to produce real-world scenarios with the students as much as possible.

 It's a really easy product in AWS. It's easy to teach and easy to understand.

We considered Puppet and Ansible. We went with Chef because Chef uses Ruby and Ruby is pretty popular right now.

Compare it to the other services that you use.

Everything can always be improved. If you have a specific need in configuration management and integration, Chef is a great product, especially with AWS.