experiment

README

Turing Experiments

At the heart of the capabilities offered by Turing is the Experiment Engine, which manages the experiment configurations and performs the necessary computations to select an applicable treatment, for every request made to the Turing system. Differtent organizations and use cases may require different behaviours from the Experiment Engine and may already have existing systems in place that carry out this function. Thus, Turing offers an extensible architecture where developers can create and plug in their own Experiment Engines. This sub-repo holds the interface definitions that are required to be implemented by an Experiment Engine that wishes to integrate itself into Turing.

Get Started

• Begin by understanding the Experiment Concepts in Turing
• Learn how to set up your local environment and start creating Experiment Engine plugins from the Developer Guide

Documentation

Index

• type EngineFactory
  • func NewEngineFactory(name string, cfg map[string]interface{}, logger *zap.SugaredLogger) (EngineFactory, error)

Types

type EngineFactory

type EngineFactory interface {
	GetExperimentManager() (manager.ExperimentManager, error)
	GetExperimentRunner() (runner.ExperimentRunner, error)
}

EngineFactory interface defines methods for accessing manager/runner of a given experiment engine

func NewEngineFactory

func NewEngineFactory(name string, cfg map[string]interface{}, logger *zap.SugaredLogger) (EngineFactory, error)

NewEngineFactory is a constructor method that creates a new instance of EngineFactory The concrete implementation of EngineFactory can be either:

• experiment/plugin/inproc/factory (for experiment engines implemented as compile-time plugins)
• experiment/plugin/rpc/factory (for experiment engines implemented as external net/rpc plugins)

The actual implementation is determined based on provided engine configuration (passed via `cfg`)