API / backend
Use case
An API without a frontend, focused on execution and database resources.
Workload assumptions
- Monthly page views
- 0 PV
- Page size
- 0 KB
- Media storage
- 0 GB
- Media transfer
- 0 GB
- Monthly active users
- 5,000 MAU
- Database storage
- 0.3 GB
- Function invocations
- 1,500,000 calls
- Requests per PV
- 1 calls
- Dynamic request ratio
- 1 0-1
- Monthly uploads
- 0 items
- Media requests per PV
- 0 calls
- Monthly updates
- 10 calls