What is our primary use case?
My main use case for LaunchDarkly is feature flagging and gradual rollouts. Instead of releasing a new feature to all users at once, we can first enable it for internal users, then for a small group of customers, and only later roll it out to everyone.
When we released a new feature, we first turned it on only for internal users. After that, we enabled it for a small percentage of real customers, which helped us test that feature in production without taking too much risk. If something went wrong, we could simply turn the flag off in LaunchDarkly without doing a full rollback.
We use flags for gradual deploying and testing, then rolling out. For example, we enabled a feature, tested it in a specific environment, then turned off this flag.
What is most valuable?
The best feature LaunchDarkly offers is the flag that allows rollouts.
What I appreciate about LaunchDarkly is that the setup was easy, it had a clean user experience, and the control allowed us to manage the features without deploying them to everyone. We could deploy it gradually and then roll out easily. I particularly value the ability to click to turn the feature on and off.
LaunchDarkly has positively impacted my organization by reducing the risk of releasing new features because we did not have to expose everything to all users at the same time. It eventually resulted in faster releases and more confidence. It also saved engineering time because in some cases, we did not need to do a rollback or hot fixes; we could simply disable the feature flag. Additionally, it reduced the QA time since they could only test a specific area.
What needs improvement?
LaunchDarkly can be improved by managing old flags. We have an issue with old flags; it became very messy very fast and we need to be very disciplined about managing these flags. I also heard from the manager that it was very expensive when the usage grew.
Perhaps LaunchDarkly could mark old flags somehow or add a tag to these flags when they are not in use or have not been used for a long time. We found ourselves after a short period of time having too many flags.
For how long have I used the solution?
I have been working in my current field for above ten years.
Which solution did I use previously and why did I switch?
I used LaunchDarkly in my previous company for several months.
What other advice do I have?
Overall, LaunchDarkly saved our engineering time and helped us manage features very smoothly, allowing us to gradually deploy and roll out.
My advice for others looking into using LaunchDarkly is to manage the flags carefully, as it can become messy very fast.
I believe LaunchDarkly is a very useful tool for teams wanting to release features quickly and safely; it gives a lot of control and helps reduce the risk around production releases. I would rate this product an eight out of ten.
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?