This repository houses the .Net based C# SDK for use with Optimizely Full Stack and Optimizely Rollouts.
Optimizely Full Stack is A/B testing and feature flag management for product development teams. Experiment in any application. Make every feature on your roadmap an opportunity to learn. Learn more at https://www.optimizely.com/platform/full-stack/, or see the documentation.
Optimizely Rollouts is free feature flags for development teams. Easily roll out and roll back features in any application without code deploys. Mitigate risk for every feature on your roadmap. Learn more at https://www.optimizely.com/rollouts/, or see the documentation.
The SDK can be installed through NuGet:
PM> Install-Package Optimizely.SDK
An ASP.Net MVC sample project demonstrating how to use the SDK is available as well:
PM> Install-Package Optimizely.SDK.Sample
Simply compile and run the Sample application to see it in use. Note that the way the Demo App stores data in memory is not recommended for production use and is merely illustrates how to use the SDK.
See the Optimizely Full Stack developer documentation to learn how to set up your first Full Stack project and use the SDK.
Create the Optimizely Client, for example:
private static Optimizely Optimizely =
new Optimizely(
datafile: myProjectConfig,
eventDispatcher: myEventDispatcher,
logger: myLogger,
errorHandler: myErrorHandler,
skipJsonValidation: false);
Since this class parses the Project Config file, you should not create this per request.
This class exposes three main calls:
- Activate
- Track
- GetVariation
Activate and Track are used in the demonstration app. See the Optimizely documentation regarding how to use these.
The Optimizely client object accepts the following plug-ins:
IEventDispatcherhandles the HTTP requests to Optimizely. The default implementation is an asynchronous "fire and forget".ILoggerexposes a single method, Log, to record activity in the SDK. An example of a class to bridge the SDK's Log to Log4Net is provided in the Demo Application.IErrorHandlerallows you to implement custom logic when Exceptions are thrown. Note that Exception information is already included in the Log.ProjectConfigManagerexposes method for retrieving ProjectConfig instance. Examples includeFallbackProjectConfigManagerandHttpProjectConfigManager.EventProcessorprovides an intermediary processing stage within event production. It's assumed that the EventProcessor dispatches events via a provided EventDispatcher. Examples includeForwardingEventProcessorandBatchEventProcessor. These are optional plug-ins and default behavior is implement if none are provided.
OptimizelyFactory
provides basic utility to instantiate the Optimizely SDK with a minimal number of configuration options.
OptimizelyFactory does not capture all configuration and initialization options. For more use cases,
build the resources via their respective builder classes.
You must provide the SDK key at runtime, either directly via the factory method:
Optimizely optimizely = OptimizelyFactory.newDefaultInstance(<<SDK_KEY>>);
You can also provide default datafile with the SDK key.
Optimizely optimizely = OptimizelyFactory.newDefaultInstance(<<SDK_KEY>>, <<Fallback>>);
OptimizelyFactory provides support of setting configuration variables in App.config: User can provide variables using following procedure:
- In App.config file of your project in add following:
<configSections>
<section name="optlySDKConfigSection"
type="OptimizelySDK.OptimizelySDKConfigSection, OptimizelySDK, Version=3.2.0.0, Culture=neutral, PublicKeyToken=null" />
</configSections>
- Now add optlySDKConfigSection below . In this section you can add and set following HttpProjectConfigManager and BatchEventProcessor variables:
<optlySDKConfigSection>
<HttpProjectConfig sdkKey="43214321"
url="www.testurl.com"
format="https://cdn.optimizely.com/data/{0}.json"
pollingInterval="2000"
blockingTimeOutPeriod="10000"
datafileAccessToken="testingtoken123"
autoUpdate="true"
defaultStart="true">
</HttpProjectConfig>
<BatchEventProcessor batchSize="10"
flushInterval="2000"
timeoutInterval="10000"
defaultStart="true">
</BatchEventProcessor>
</optlySDKConfigSection>
- After setting these variables you can instantiate the Optimizely SDK using function:
Optimizely optimizely = OptimizelyFactory.newDefaultInstance();
BatchEventProcessor is a batched implementation of the EventProcessor * Events passed to the BatchEventProcessor are immediately added to a BlockingQueue. * The BatchEventProcessor maintains a single consumer thread that pulls events off of the BlockingQueue and buffers them for either a configured batch size or for a maximum duration before the resulting LogEvent is sent to the NotificationManager.
EventProcessor eventProcessor = new BatchEventProcessor.Builder()
.WithMaxBatchSize(MaxEventBatchSize)
.WithFlushInterval(MaxEventFlushInterval)
.WithEventDispatcher(eventDispatcher)
.WithNotificationCenter(notificationCenter)
.Build();
The Max event batch size is used to limit eventQueue batch size and events will be dispatched when limit reaches.
The FlushInterval is used to specify a delay between consecutive flush events call. Event batch will be dispatched after meeting this specified timeSpan.
Custom EventDispatcher can be passed.
Custom NotificationCenter can be passed.
HttpProjectConfigManager
is an implementation of the abstract PollingProjectConfigManager.
The Poll method is extended and makes an HTTP GET request to the configured URL to asynchronously download the
project datafile and initialize an instance of the ProjectConfig.
By default, HttpProjectConfigManager will block until the first successful datafile retrieval, up to a configurable timeout.
Set the frequency of the polling method and the blocking timeout with HttpProjectConfigManager.Builder.
HttpProjectConfigManager httpManager = new HttpProjectConfigManager.Builder()
.WithSdkKey(sdkKey)
.WithPollingInterval(TimeSpan.FromMinutes(1))
.Build();
The SDK key is used to compose the outbound HTTP request to the default datafile location on the Optimizely CDN.
The polling interval is used to specify a fixed delay between consecutive HTTP requests for the datafile. Between 1 to 4294967294 miliseconds is valid duration. Otherwise default 5 minutes will be used.
The blocking timeout period is used to specify a maximum time to wait for initial bootstrapping. Between 1 to 4294967294 miliseconds is valid blocking timeout period. Otherwise default value 15 seconds will be used.
You can provide an initial datafile via the builder to bootstrap the ProjectConfigManager so that it can be used immediately without blocking execution.
The URL is used to specify the location of datafile.
This option enables user to provide a custom URL format to fetch the datafile.
This option is used to specify whether to start the config manager on initialization or not. If no value is provided, by default it is true and will start polling datafile from remote immediately.
This option is used to provide token for datafile belonging to a secure environment.
The sample project contains unit tests as well which can be run from the built-in Visual Studio Test Runner.
Please see CONTRIBUTING.
Optimizely SDK uses third party software: murmurhash-signed, Newtonsoft.Json, and NJsonSchema.