What is our primary use case?
Our main use case for LaunchDarkly is managing our releases and introducing new features to our data pipelines. We put our new features behind LaunchDarkly flags, which helps us enable or disable them at will, so that we can run our data pipelines with or without those features. That makes rollbacks very easy, and it also helps us with A/B testing. This is important for us because we need to make sure that our data pipeline produces correct data. If, for example, any feature messes up the data, we can disable it, run the pipeline again without that code path, and get the correct data that we generate. That is how we use LaunchDarkly.
We mostly use it in that way.
With AI coding tools helping our team ship code faster, LaunchDarkly helps us maintain control once that code hits production by making our deployments very precise. Using the rules we can set in each flag, we can precisely enable a flag for a few test tenants or test users first. If everything goes fine with them, they do not report any issues, and we do not see any difference in our own metrics, then we go ahead and deploy it or enable it for everyone.
With AI tools helping us write some of our code, we now create a lot more flags with LaunchDarkly, and we also do a lot more cleanup. I think that is expected when you have this velocity.
We do not use integrations such as AWS, GitHub, Sentry, New Relic, Anthropic, or others with LaunchDarkly.
How has it helped my organization?
Using LaunchDarkly for feature flags and A/B testing changes my day-to-day workflow by reducing the tiring work of constantly merging our changes and then reverting them. We do not have to go through all of those merge and revert MRs when we use LaunchDarkly flags, so it speeds up the whole process.
LaunchDarkly has impacted our organization positively by helping our entire organization move faster. It helps us deploy features faster. I think one of the most important capabilities is that you can do a lot of differentiation. For example, we use Apache Airflow, where we have multiple DAGs, and inside those DAGs we have multiple tenants. We can specifically disable or enable a feature for one particular DAG. Before rolling out to all tenants or all the DAGs, we can precisely run the feature for one of the tenants, verify it first, and then do a wider rollout. Staged rollout is also one of the features that helps a lot.
Our deployment speed has increased by about 30% since we started using LaunchDarkly. We are rolling out more features sooner because we have the option of doing staged rollouts and of quickly reverting the features that do not work as intended.
Since implementing LaunchDarkly, I have seen measurable improvements, and the latency has improved.
What is most valuable?
I think the best features LaunchDarkly offers are the dashboard, which is very helpful, and the different environments you can create. All of those environments get evaluated differently, so we do not have to make any differentiation in the code itself. Depending on the environment the request originates from when it checks the value of the flag, LaunchDarkly automatically makes sure that only the value for that environment is served. That is very useful. The dashboard is also very useful for seeing all the flags we have and for later cleanup if we need to delete any flags. We also have the audit history, which shows who turned on a flag, and that is very helpful as well.
The audit history and environment separation features help our team in practice because we sometimes need to differentiate between environments. We have a pre-prod environment before prod, so we can usually turn the flag on or off in pre-prod and test. That is where the differentiation of environments helps. The audit history is helpful because we are a cross-functional team, and there are teams that create their own LaunchDarkly flags so they can enable or disable them. We can know who is enabling or disabling a flag and make sure we have an audit, at least, so that we can point out who has flipped the flag.
What needs improvement?
I think LaunchDarkly can be improved in the hierarchy of some of the rules we set to precisely enable or disable some DAGs. It is not very intuitive. The way it is shown, you would not know that the order of those rules matters.
From what I have noticed, that is the only improvement that would help.
For how long have I used the solution?
I have been using LaunchDarkly for the past year.
What do I think about the stability of the solution?
LaunchDarkly is pretty stable. The uptime is good, and I do not have any issues with uptime.
What do I think about the scalability of the solution?
LaunchDarkly's scalability is strong because we have not faced any issues, even with a million requests per day for most of the flags. It is pretty scalable.
How are customer service and support?
We never contact customer support because we mostly do not have to.
Which solution did I use previously and why did I switch?
Before LaunchDarkly, we were not using any solution, to be honest. We were introduced to this new category of product, which is staged rollout and related capabilities. It is a new solution that our organization came up with to increase deployment speed and reliability.
We do not use any previous or different solution, so LaunchDarkly is our first.
What was our ROI?
I would say LaunchDarkly has saved a lot of time, and it is not that expensive either. We have saved about 20% of our time, since we would otherwise be unnecessarily spending it on reverting rollouts to production.
What's my experience with pricing, setup cost, and licensing?
The IT team handles all the purchases.
Our experience with pricing, setup cost, and licensing is fine. We are on the Enterprise plan with around 120 seats, which is fine for us.
Which other solutions did I evaluate?
When comparing LaunchDarkly to alternative solutions, I am just an engineer who leads the way. In terms of competitors, we are not aware of many. LaunchDarkly is the one that came up, and we just got to work with it.
Before choosing LaunchDarkly, we did not evaluate other options.
What other advice do I have?
On a scale of 1 to 10, I would rate LaunchDarkly a solid eight.
The reason I give LaunchDarkly an eight, rather than a 10 or a lower score, is that the rules can sometimes be confusing in the UI. If that were fixed, it would help. Other than that, LaunchDarkly is stable most of the time, so there is very little downtime, except for a few times. That is why I give it a solid eight.
I think LaunchDarkly is doing a decent job of disclosing its AI capabilities, governance, and security. However, it is still a black box to most users how it is being managed.
We do not use LaunchDarkly's AI capabilities a lot. From what I have heard from my colleagues on some of the teams, it is decent, albeit a bit expensive.
LaunchDarkly is deployed in our organization on public cloud only.
The ops team will know exactly where they have deployed it, but we are mostly using AWS.
My advice to others looking into using LaunchDarkly is to make sure that, since you are doing so many releases or deployments, you have a way to go back and revert those changes. That helps you quickly fix whatever issues might arise due to the volume of MRs that are being merged.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.