Togle is a cloud-based time tracking tool that is widely used by freelancers and students. It features precise reporting capacity, available on a wide variety of platforms and is designed to provide idle detection and accurate tracking reminders.

Feature Toggle Configuration – How to Manage

In a shared system where toggle configuration is dynamically re-configured re-deploying toggle configuration files into testing environments can be an inefficient process. This is especially true if you have large numbers of toggles or a large number of feature flags to re-configure.

Feature Toggle Configuration in a Central Store

Many organizations choose to move Toggle Configuration into some type of central store, often an existing application DB. This allows system operators, testers and product managers to view and modify toggle configuration from an admin UI.

Using static files for managing toggle configuration is fine until you get to a certain scale, at which point it can become more fiddly than necessary. This becomes even more of an issue when you use a lot of complex feature flags.

Experiment Toggleconfig

The ability to re-configure toggles at runtime is a very useful technique for conducting A/B testing. For example, if you want to test the effect of different code paths on a particular feature, you can configure an experiment toggle that will re-configure every user in the system and send them down one or the other path at runtime.

However, it is important to remember that re-configuring toggles at runtime is very inefficient and should only be done as part of an automated test. In a production environment you should instead use a more general-purpose mechanism like a real distributed configuration system.