When your app gets popular
Published Updated
This is the Learning Atlas from Orbit. Get your invite
HostinginfrastructuredatabasesConcepts and methodology
-
Step 1: Cache
Why this matters here
Start by reusing safe copies of repeated reads to reduce work as visitors increase.
In short
A stored copy of data that is faster to read than fetching or calculating the original again.
-
Step 2: Rate limit
Why this matters here
Next protect the app by limiting how many requests each caller may send.
In short
A deliberate restriction put in place by an API provider to cap the number of requests a user or system can make within a specific timeframe.
-
Step 3: Load balancer
Why this matters here
When several app copies are needed, distribute incoming requests among healthy copies.
In short
A traffic distributor that sends incoming requests to available copies of your application.
-
Step 4: Reverse proxy
Why this matters here
Then learn how a public entry point forwards requests to the right app server.
In short
A server in front of your app that receives requests and forwards them to the appropriate app server.
-
Step 5: API gateway
Why this matters here
Finally bring several APIs behind one entry point with shared access and traffic policies.
In short
A shared entry point for application programming interfaces that routes requests and applies common access or traffic rules.
Full definition of API gateway →
Continue with When a call fails: timeouts, retries and doing it once →