stateless architecture
An architecture in which each SDK pulls a static JSON file from CloudBees Feature Management cloud storage. CloudBees Feature Management uses a stateless architecture by default.
The CloudBees Feature Management stateless architecture has a few 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 CloudBees Feature Management servers. All flag computation is done in the memory on the target platform.
-
Resiliency - CloudBees Feature Management servers are NOT in the critical path of your software. If CloudBees Feature Management is not responding, you cannot make flag changes via the dashboard but your application is not affected. Also, the SDKs have a caching mechanism. In the case of a network issue, the effects are minimal as well.
-
Privacy - CloudBees Feature Management does not send or know any of your users' private data; everything happens on the target application.
-
Global Usage - CloudBees Feature Management leverages the power of Amazon CloudFront for its Content Delivery Network. The deliberate inclusion of CloudFront in our architecture provides a unique advantage over other technologies' CDN systems that report outages and difficulties in certain geographic areas. In short, 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.