Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Pretty straightforward, but lacking in API reporting
What do you like best about the product?
It seems relatively straightforward to and helps streamline the feature flag process.
What do you dislike about the product?
The backend API is lacking for reporting purposes. It's very difficult to find out what segments have the feature flag enabled for example.
What problems is the product solving and how is that benefiting you?
It helps deploy new features selectively to segments of users. We can also immediately turn off a feature if there is a problem.
- Leave a Comment |
- Mark review as helpful
A flexible UX for controlling new features dynamically
What do you like best about the product?
When rolling out a new feature, whether customer-facing or not, it's important to dynamically enable that feature, on varying environments, and then, incrementally on "alpha", "beta", and then the entire customer base, in small batches at a time. We use LD for these scenarios -- the features can be defined as simple booleans or integers, or as JSON hash-values deliverying varying combinations of values in one query.
This LD-based incremental approach is especially useful for transitioning "old" code to new code, say where the new code is making network calls to a new microservice, which increases both performance and complexity, especially with error management.
We have successfuly mananged several such transitions with LD controls as we address tech-debt with modern, domain-based code, including increased use of varying languages across many internal microservices.
That these LD controls can be partitioned by team ownership helps with cross-functional collaboration.
Finally, using LD feature controls also enables stakeholders from non-Engineering treams, such as Product Managers, Customer Success, Developer Success, etc. to participate in the rollout and control of these new features, as needed.
This LD-based incremental approach is especially useful for transitioning "old" code to new code, say where the new code is making network calls to a new microservice, which increases both performance and complexity, especially with error management.
We have successfuly mananged several such transitions with LD controls as we address tech-debt with modern, domain-based code, including increased use of varying languages across many internal microservices.
That these LD controls can be partitioned by team ownership helps with cross-functional collaboration.
Finally, using LD feature controls also enables stakeholders from non-Engineering treams, such as Product Managers, Customer Success, Developer Success, etc. to participate in the rollout and control of these new features, as needed.
What do you dislike about the product?
The downsides to using LD controls for new features is that these controls can sometimes become "permanent", in that they work for many stakeholders, but are not actually within our own product controls, and thus incur a permanent cost.
These controls are also network-based, which in some circumstances adds latency to the simple act of controlling a feature.
These controls are also network-based, which in some circumstances adds latency to the simple act of controlling a feature.
What problems is the product solving and how is that benefiting you?
LD helps us transition from "old" code to new code gradually, incrementally, across multiple operating environments from the same UI.
We can deploy new code, without worrying about breaking existing production through the use of LD feature flags around the new code, and then, incrementally enable and test the new features in various environments.
This includes the eventual migration of processing from the old code to the new code, incrementally across customers.
Having LD features owned by various teams is also a very useful feature that helps our teams manage our own feature flags.
We can deploy new code, without worrying about breaking existing production through the use of LD feature flags around the new code, and then, incrementally enable and test the new features in various environments.
This includes the eventual migration of processing from the old code to the new code, incrementally across customers.
Having LD features owned by various teams is also a very useful feature that helps our teams manage our own feature flags.
Easy to use, full fledged system that works across tech stacks
What do you like best about the product?
It is reliable; the client frameworks have efficient caches built in and as a developer, I dont have to worry if adding a feature flag will have a performance impact.
What do you dislike about the product?
Obviously it is a cost that could be solved with an open source solution. But when your scale is so large that managing a feature flag system is a cost in itself, it makes sense to consider the already built solution.
What problems is the product solving and how is that benefiting you?
Managining features flags, gradual rollouts, etc.
Best tool to control feature releases
What do you like best about the product?
The UX of launch darkly is quite simple, which makes it really easy to use
What do you dislike about the product?
The recent addition of predefined flags, I'd rather use them all as custom flags
What problems is the product solving and how is that benefiting you?
It allows me to control when to release a feature, and also prevent new bugs from happening. If there's a bug, I can turn off the flag immediately.
Experimentation simplified
What do you like best about the product?
The user experience is great and the layout is straightforward. You can configure experiments based on customizable attributes like user ID, email etc. to ensure only your target cohort sees the A/B test experience
What do you dislike about the product?
If you want to update a flag in multiple enviornments you need to go into configurations for each enviornment and update them separately. Would be nice to have tabs or a way to navigate on the same screen between different environments
What problems is the product solving and how is that benefiting you?
Running experiments for feature launches
Amazing product
What do you like best about the product?
An amazing product with lots of functionality and features. It's easy to use, friendly, and the live updated are an amazing added bonus. We use this product a lot.
What do you dislike about the product?
Nothing really, don't hesitate to switch.
What problems is the product solving and how is that benefiting you?
Releasing features gradualy without risks. Great control on who sees the feature and who's not.
Works, but ui is very confusing and misleading
What do you like best about the product?
That it works...........................
What do you dislike about the product?
The ui is very confusing. You need to simplify it a lot for LaunchDarkly to be well-understood.
Other then that - better understanding of your architecture will be appreciated (how the agent in the app effects scaling)
Other then that - better understanding of your architecture will be appreciated (how the agent in the app effects scaling)
What problems is the product solving and how is that benefiting you?
avoiding deployment for reverting new changes
Seamless feature releases made easy with LaunchDarkly
What do you like best about the product?
What I like best about LaunchDarkly is its simplicity and effectiveness in managing feature releases. With LaunchDarkly, implementing feature flags and managing feature rollouts becomes incredibly straightforward.
What do you dislike about the product?
The new UX - I am working with LD for a few years and I got used to the old UX.
What problems is the product solving and how is that benefiting you?
1. LaunchDarkly solves the problem of selectively releasing features for internal testing. With LaunchDarkly, we can easily restrict access to new features, allowing only internal teams to test them before rolling them out to all users.
2. LaunchDarkly facilitates gradual feature releases. This means we can open a feature to a small subset of users first, gradually expanding access to all users. This approach allows us to carefully monitor the impact of new features and ensure a smooth rollout for all users.
2. LaunchDarkly facilitates gradual feature releases. This means we can open a feature to a small subset of users first, gradually expanding access to all users. This approach allows us to carefully monitor the impact of new features and ensure a smooth rollout for all users.
Effective, fun and convenient to work with LD
What do you like best about the product?
The convenience of viewing and simplicity, without too many complications, you can tell from the main page which feature flags serve true/false and the statistics and the ease of operation.
What do you dislike about the product?
Many times I want to get a snapshot of a certain feature (which can include several feature flags or even different accounts under LD) and apart from manually going through each of the feature flags, I don't have a convenient way to do it.
So both in terms of viewing and in terms of control, I would be happy to unify the number of feature flags under the same "group" for viewing/control.
So both in terms of viewing and in terms of control, I would be happy to unify the number of feature flags under the same "group" for viewing/control.
What problems is the product solving and how is that benefiting you?
The danger of changing a code that many rely on separately without testing it gradually/possibility to turn it off if something happens.
LD meets exactly this need.
LD meets exactly this need.
Works well but per-user pricing is a bit ridiculous
What do you like best about the product?
Seems to offer anything and everything you could need for tests, and manages to do it very performantly.
What do you dislike about the product?
The pricing per-user is prohibitively expensive. It shouldn't make any difference if we have one user administering our tests or 100. Pricing should depend on things like the volume of invocations. It really just encourages either account sharing or being stingy with access - both of which hurt LD more than they help.
What problems is the product solving and how is that benefiting you?
Low latency variant cohorting for end users. It helps us in that we already had a solution for this but it added latency overhead to requests which LaunchDarkly is able to avoid.
showing 31 - 40