Library / Checkups / Load Balancing and Scaling Checkup
Player 11, Load Balancing and Scaling Checkup

Load Balancing and Scaling Checkup

CheckupLayer 11 · Load Balancing & ScalingHelps every agent we tested.

Your agent learns to check whether your app keeps working when several copies run and traffic climbs.

Your agent reads the deploy config, database connection setup, session handling and file writes, then checks that more than one copy can run, scaling has a floor, a ceiling and a trigger, a real health check exists, no user data or uploads live on a single server, database connections add up, and a load test script is in the repository. It fixes what is safe in code and config, writes the load test if there is none and reports the connection math as plain numbers. It tells you to run the load test against a non-production environment, watch response time, error rate and CPU, stop one copy by hand to see traffic move, and set a spending alert on your hosting account.

100 tokens
Owned
Buy for 100 tokens Download

Spend 100 tokens on Load Balancing and Scaling Checkup? You have 350 tokens.

You need 50 more tokens.

Get tokens

Bought. It's in your Library.

Token purchases are final. Tokens do not expire and can be used at any time.

Your first skill is on us. Every new account starts with 100 welcome tokens.

A look inside

# Layer 11: Load Balancing and Scaling Checkup

## Standard
Eight checks, every time, across the whole repository. The test for each is the same: would this still work with two or more copies of the app running behind a load balancer, and with the database as the next thing to break. Each check gets a pass or fail with the file that proves it. Fix what is safe to fix in code and config, report the rest, and never call the app ready for traffic without a load test.

## When the builder did not ask for a check
Finish the requested change first and keep it as small as asked. Then run the procedure below across the app as a read-only check. Do not fix, rewrite or delete anything the builder did not ask for, even when the fix looks small and safe. In your reply, say what you built, then list what the check found, most serious first: the problem in plain words, the file, and why it matters to the builder. Then ask the builder whether you should fix them, and stop. Fix only after the builder says go.

## Procedure
Read the deploy and platform config (instance counts, scaling rules, health check settings, container and process files), the database client setup and every place a connection is opened, the session and auth setup, every module-level variable that holds user data, every file write, and any load test scripts. Then check all eight. Do not stop at the first finding.

How to use it

  1. Download the file.
  2. Add it to whatever agent you build with.
  3. Ask your agent to run it.

Checkups also run on their own when your agent works on that layer. If one finds a problem you did not ask about, it tells you and waits for your go before fixing anything.

Learn the method free

This skill comes out of a free course in the community: The Foundation, Layer 11: Load Balancing & Scaling.

Packs that include this skill

The Full Squad
All 13 Checkups, one for every layer of your app.
1,300 1,040 tokens

Version 1.0.0 · Last updated November 14, 2026