-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Our endpoint needs to withstand large amounts of traffic. The API endpoint will take gateId and walletAddress
Requirements:
- A cache-header for example 5s. If the same GET request is made with the same wallet address and gateId it will return the cached result
Ideas:
- If the same
user X needs to follow twitter account Yis being used in multiple gates that result should be cached and not needed to be resolved multiple times at the same time interval.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels