Chef vs LaunchDarkly comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Chef
Ranking in Build Automation
16th
Average Rating
8.0
Number of Reviews
18
Ranking in other categories
Release Automation (15th), Configuration Management (17th)
LaunchDarkly
Ranking in Build Automation
40th
Average Rating
7.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Aaron  P - PeerSpot reviewer
Sep 18, 2023
Easy configuration management, optimization abilities, and complete infrastructure and application automation
Chef is like a master chef in a kitchen for computer systems. It's used to create recipes (cookbooks) that specify how servers and apps should be set up. Chef then makes sure these instructions are followed the same way on all computers in a network. The ChefServer is like the recipe book, where…
Suresh Chaudhari - PeerSpot reviewer
Jun 28, 2024
Supports trunk-based development, allowing for faster development but lacks multi-region support
LaunchDarkly currently lacks multi-region support. I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down. They should have a backup URL and collaborate with other engineers to ensure availability. There should be a fail-over strategy in place. My understanding is that a multi-region real-time solution isn't available yet. Another future enhancement I envision is having the entire application property load through LaunchDarkly. This integration would be advantageous but needs to be designed to be very user-friendly and serviceable. I use a dashboard. I see some improvements happening, but it's a little bit cluttered. It even needs to be improved because certain kinds of levels of fields are added. So they need to make it very user-friendly, that kind of thing. So, LaunchDarkly really has to play around and make it very user-friendly. I expect certain behavior from the tool, but it gives me false results. I know I need to play around with all the properties, and then I can go to what it takes. It's not a tool that a non-technical person can use. Like, whoever is a non-technical person can also easily able to understand what they want to do; that kind of thing used to be taken as part of the dashboard (cloud dashboard), which is wherever we are enabled with your feature, like, so because If you go inside the plans, it has, like, a certain level of conditions and operations. So sometimes it works well, sometimes it doesn't work. So everyone has to understand. So, that needs to be very precise.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations."
"If you're handy enough with DSL and you can present your own front-facing interface to your developers, then you can actually have a lot more granular control with Chef in operations over what developers can perform and what they can't."
"The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools."
"This solution has improved my organization in the way that deployment has become very quick and orchestration is easy. If we have thousands of servers we can easily deploy in a small amount of time. We can deploy the applications or any kind of announcements in much less time."
"One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over."
"Chef can be scaled as needed. The Chef server itself can scale but it depends on the available resources. You can upgrade specific resources to meet the demand. Similarly, with clients, you can add as many clients as you need. Again, this depends on the server resources. If the server has enough resources, it can handle the number of servers required to manage the infrastructure. Chef can be scaled to meet the needs of the infrastructure being managed."
"The product is useful for automating processes."
"It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop."
"It has really helped during the series of product lines and faster deployment and faster development."
 

Cons

"The solution could improve in managing role-based access. This would be helpful."
"There appears to be no effort to fix the command line utility functionality, which is definitely broken, provides a false positive for a result when you perform the operation, and doesn't work."
"I would rate this solution a nine because our use case and whatever we need is there. Ten out of ten is perfect. We have to go to IOD and stuff so they should consider things like this to make it a ten."
"It is an old technology."
"The time that it takes in terms of integration. Cloud integration is comparatively easy, but when it comes to two-link based integrations - like trying to integrate it with any monitoring tools, or maybe some other ticketing tools - it takes longer. That is because most of the out-of-the-box integration of the APIs needs some revisiting."
"If they can improve their software to support Docker containers, it would be for the best."
"Third-party innovations need improvement, and I would like to see more integration with other platforms."
"If only Chef were easier to use and code, it would be used much more widely by the community."
"I strongly believe they need to develop a strategy for handling situations where LaunchDarkly goes down."
 

Pricing and Cost Advice

"The price per node is a little weird. It doesn't scale along with your organization. If you're truly utilizing Chef to its fullest, then the number of nodes which are being utilized in any particular day might scale or change based on your Auto Scaling groups. How do you keep track of that or audit it? Then, how do you appropriately license it? It's difficult."
"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."
"When we're rolling out a new server, we're not using the AWS Marketplace AMI, we're using our own AMI, but we are paying them a licensing fee."
"We are able to save in development time, deployment time, and it makes it easier to manage the environments."
"Purchasing the solution from AWS Marketplace was a good experience. AWS's pricing is pretty in line with the product's regular pricing. Though instance-wise, AWS is not the cheapest in the market."
"I wasn't involved in the purchasing, but I am pretty sure that we are happy with the current pricing and licensing since it never comes up."
"Pricing for Chef is high."
"We are using the free, open source version of the software, which we are happy with at this time."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
792,098 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
14%
Manufacturing Company
8%
Government
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Chef?
Chef is a great tool for an automation person who wants to do configuration management with infrastructure as a code.
What needs improvement with Chef?
Chef does not support the containerized things of Chef products. In the future, Chef could develop a docker container or docker images.
Ask a question
Earn 20 points
 

Comparisons

No data available
 

Learn More

 

Overview

 

Sample Customers

Facebook, Standard Bank, GE Capital, Nordstrom, Optum, Barclays, IGN, General Motors, Scholastic, Riot Games, NCR, Gap
Information Not Available
Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation. Updated: June 2024.
792,098 professionals have used our research since 2012.