Why use Split for PHP?
Split’s PHP SDK brings scalable feature flagging to any app, website or experience built in PHP. Split helps teams control rollouts, and customer experiences, while gathering new data and insight on how their products are being engaged. With Split, teams can:
- Release features to production but disabled for all users by default
- Target new features only to internal QA teams
- Slowly roll out features to a broader audience by percentage, demographic, geography, account type, or any other metric
- Kill features with a single click to revert back to your safe state
Split works across many different languages, letting developers, PMs and support teams control feature rollout from one unified view—and monitor the success of any new code. Our integrations bring rollout updates into the tools your team is already using, further opening the feature-delivery process up to your entire organization.
Split’s PHP SDK Architecture
Because of the share nothing-nature of PHP, the PHP SDK architecture is different from other SDKs. The SDK has three components:
- The Synchronizer Service is responsible for fetching the data from Split servers it needs to evaluate what treatment to show to a customer. It is a background service that can be run on one machine on a schedule via your scheduling system. We recommend supervisord.
- The cache component is where the Synchronizer Service stores its fetched data. The SDK comes pre-packaged with a Redis Cache Adapter. It is critical that Redis is configured to never evict.
- The SDK client is embedded within your PHP app. It is the brains that decides which treatment to show to a customer for a particular split.
Visit our documentation to learn more about Split’s PHP architecture considerations.
Getting Started with Split for PHP
Split’s PHP SDK is very simple to integrate into your code base and is completely open source. All it really takes to get rolling with Split is initiating the SDK, then splitting your code.
View the documentation and start building today.