CloudWinks · Foundation apps

ScalingSusanTechnical brief

ScalingSusan holds information used to manage speed, service health and how work is spread across servers. It describes cache entries, endpoint health and failover behavior for the platform.

Read the business brief · PDF

1. Architecture in brief

ScalingSusan is a Foundation app with platform tenancy. It holds cache metadata and endpoint-health records, which can point at a CloudWinks application. Flutter services describe memory and disk caches, a load balancer, health checks, retries and a circuit breaker. CloudWinks supplies the application runtime. The product model is this information layer; it does not by itself operate a particular cluster.

2. Service boundary and intake

Cache keys, tags, levels and expiry are recorded when a value is stored or invalidated. Endpoint health is recorded when a check runs, including response time, success and failure counts and circuit-breaker state. Client services may sit in front of platform API calls. Credentials are not taken in as cache or health fields.

3. Data handled

The model stores cache keys, tags, expiry, access counts and cache level, and endpoint URLs with health, timings, failure counts and circuit-breaker state. ScalingSusan owns these records. It does not own the business payload being cached, the KeyKook secret or a separate Redis or proxy product.

4. Integrations and ownership

CloudWinks can be named on a cache or health record. Framework API calls may use the client services. KeyKook remains the credential store. Murphy can receive check or runtime problems. ScalingSusan owns cache and health information, not those other services.

5. Security and access

Access follows platform grants. A cache key is not a grant to the underlying business record. Endpoint records should not expose credentials. Identity and access remain with Crux and KeyKook. These records are operational metadata, not customer workspaces.

Competitive context

AlternativeIts focusCloudWinks product focus
RedisIn-memory keys with expiry, used as a cache in front of a database.Cache metadata and expiry recorded in the CloudWinks platform model.
HAProxyLoad balancing with health checks and failover to a backup server.Endpoint health and circuit-breaker state kept as CloudWinks records.

Read the business brief →

← More Foundation apps apps · All application briefs · How the framework works