Looking for more discussion on getting started with feature flags and experimentation? Check out Optimizely's Developer Community to learn from other developers and share.
Optimizely Full Stack is feature management and A/B testing for product teams.
- Feature flags and rollouts help you launch features safely and give you a kill switch if unanticipated issues arise.
- Feature tests empower you to experiment with feature configurations and iterate on features without deploying code. Optimizely's industry-leading Stats Engine calculates results so you can learn what's working and why.
- Full Stack A/B tests enable you to run experiments in any application. These require you to deploy code, so they're best used for one-off decisions such as comparing one algorithm against another.
Pair Optimizely's Full Stack and Web products to empower your entire organization—from product to marketing teams—to experiment and build an optimized customer experience.
Yes! Start a 30-day free trial of Optimizely Web and Full Stack. Run real experiments, use feature flags, and analyze results.
Full Stack SDKs are built so you can split traffic to experiments without making any network requests. Unlike some platforms, which call out to third-party servers for experiment decisions, all decisions are made in-memory using a cached copy of the datafile. The impact on latency is negligible.
In other words, Full Stack is faster because it doesn't make any blocking API requests to get decisions about which experiment variant to use; the device (your mobile phone or server) running the code makes that decision in under a millisecond. Full Stack won't slow down your end user's experience. However, there are still a few performance considerations to keep in mind as you scale your usage of Full Stack:
- When and how often to download the datafile that in-memory bucketing uses. Manage this by limiting the file size and download frequency.
- When and how often to send data about conversion events for tracking. Manage this by batching events and using asynchronous event dispatching (having the app send data out-of-band later).
We're always happy to discuss performance. Please contact us if you’re interested in seeing performance benchmarks for any of our SDKs.
You can experiment anywhere in your technology stack with Optimizely's SDKs. If your plan includes Full Stack, you can run experiments in various languages. If you're interested in testing in a different language, please contact us.
It’s important that your users have a consistent, delightful experience. Full Stack SDKs use deterministic bucketing via MurmurHash3 to determine which experiments and variations should be active for a user. This ensures that users will be given the same treatment across multiple visits or on different channels.
Optimizely also ensures that all of our SDKs give the same output no matter what language you’re using.
The datafile is language-agnostic. You can use the same datafile from the same project across different SDKs and get consistent bucketing. This way, you can activate and track the exact same experiments across different SDKs and get consistent results.
With access to Optimizely raw data, you can export the raw events from AWS S3.
Optimizely Full Stack SDKs support bot detection as of version 2.1. Enable bot filtering directly from your account’s project settings. Once the setting is enabled, events sent from web browsers have bot filtering applied automatically. Applying bot filtering to events sent from other environments requires configuration. For more context, read about bot filtering.
Full Stack is built for product teams. Developers work with our SDKs—but on many teams, product managers and analysts with less technical expertise configure features and experiments, manage rollouts, and analyze results in Optimizely Full Stack.
There’s no limit to the number of collaborators on an account. We encourage you to invite the whole team to increase visibility, share results and insights, and deepen experimentation across your working group. Optimizely offers a full suite of permissions and additional integrated program management tools, so your team can collaborate more effectively.
Changes in your app depend on how frequently you refresh your datafile. Changes are reflected in the datafile within ~60 seconds.
No network requests are required to evaluate feature flags and experiments, so there's no added latency. Fetch the datafile in advance—the SDK only needs access to the datafile contents. Download the datafile out-of-band from serving an individual request from your users.
After the datafile is downloaded, no network requests are needed to serve features to users. However, the SDK will still send network requests to track events. You can control when and how this happens by implementing a custom event dispatcher. For more information on event dispatchers, see the event dispatcher configuration topic for your SDK].
An app.optimizely.com interruption won't affect your app’s operation. However, during the interruption, you won't be able to log into the site to update experiments or make other changes.
Here's the Optimizely status page.
Yes, you can use Full Stack using a local copy of your datafile and batch up events to send later when your app is back online.
Yes, it's possible to use Full Stack with a heavily cached site. This setup requires appropriate configuration at your CDN provider and some additional implementation in the backend. Please contact your Customer Success Manager to discuss options. Read more about content delivery networks.
You probably won't need to modify your firewall to use Full Stack. If your firewall has egress (outbound traffic) restrictions, you'll need to whitelist cdn.optimizely.com and logx.optimizely.com.
Optimizely doesn't have a concept of "requesting features." Optimizely doesn't make network calls to serve features or experiments to users, so there's zero latency. For more information, see Does Full Stack make an API call to serve features to my users?.
You can use Optimizely as a service or include the Optimizely SDK in every service. For some best practices and special considerations when implementing Full Stack, see Microservices.
Updated 2 months ago