Depending upon your development scenario, you can choose from several software development kits (SDKs) to support your CloudBees Feature Management projects.
The SDKs include setup and installation instructions for client-side and server-side installations.
CloudBees Feature Management architecture is built around privacy.
Because client-side and server-side SDKs work with flag configuration data in different ways, some CloudBees Feature Management capabilities and features are only available for a specific type of SDK.
Client-side SDKs execute code on the client’s device, such as web, mobile, desktop, or over-the-top (OTT) applications.
Refer to Client-side SDKs for a complete list of available client-side SDKs.
Server-side applications are sent to a central server to be processed. Server-side SDK’s are updated using a periodic refresh, and can process hundreds or more requests at once.
Since more steps are required for each evaluation, server-side requests can take longer to process.
Refer to Server-side SDKs for a complete list of available server side SDKs.
|SOC 2® is a Service Organization Control (SOC) framework administered by the American Institute of CPAs (AICPA) that assesses an organization’s adherence to the five Trust Service Criteria (TSC). CloudBees Feature Management is SOC 2 type II compliant. For more information, refer to SOC 2 compliance.|
CloudBees Feature Management does not have access or save end user data, such as personally identifiable information (PII).
Flag configurations that target specific customers occurs on the client-side (mobile app, web app, or a backend system) with locally available attributes and is never transmitted back to CloudBees Feature Management.
For more information, refer to Security - CloudBees Feature Management.
CloudBees Feature Management is protected from outages by using a stateless architecture by default. Each SDK pulls a static JSON file from CloudBees Feature Management cloud storage.
The CloudBees Feature Management stateless architecture has several key advantages:
Scale: It does not matter if you have hundreds of users or millions of users, the SDK fetches a static file.
Speed: No computation is done on the CloudBees Feature Management servers. All flag computation is done in memory on the target platform.
Resiliency: CloudBees Feature Management servers are NOT in the critical path of your software. If CloudBees Feature Management is down for some reason, you will simply be unable to make flag changes via the dashboard, but there will be no effect to your application. The SDKs have a caching mechanism. In the case of a network issue, the effects are minimal.
Privacy: CloudBees Feature Management does not send or know any of your user private data, everything happens on the target application.
Global Usage: CloudBees Feature Management leverages the power of Amazon CloudFront for its Content Delivery Network (CDN). The deliberate inclusion of Amazon CloudFront in our architecture provides a unique advantage over other technologies' CDN systems that report outages and difficulties in certain geographic areas. This part of the CloudBees Feature Management infrastructure alleviates developers from creating proxies or requiring bootstrapping that would otherwise be necessary to maintain a connection in problematic regions.
|CloudBees Feature Management uses Server Sent Events (SSE) to push a message to the SDKs to download a new JSON config file on config change, so changes are propagated to the clients instantly upon modification.|