aws-samples / aws-samples/lambda-refarch-mobilebackend
Doubt on "scalability" of this architecture
- Dominant language
- Objective-C
- Stars
- 587
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
The Architecture diagram states
> Mobile applications require a highly scalable backend infrastructure to support the variable usage created by mobile users. AWS Lambda runs code in response to requests and automatically manages and scales the underlying resources. Lambda Function 1 provides a synchronous endpoint for users to store and retrieve unstructured data from Amazon DynamoDB.
My doubt is the statement that this supports a "highly scalable backend". Since the API requests are served from Lambda functions which are inherently limited to 1000 concurrent connections by default. To support even 10K users using an app you would need a minimum of 10K Lambda sessions. Since this serverless architecture does not support connection pooling, many DBs will not support this amount of concurrent "clients". So my question is how is this "highly scalable"?
Contributor guide
Research direction
Start with the architecture diagram and the quoted backend description, then review the stated AWS Lambda concurrency behavior and Amazon DynamoDB access model. Done should mean documenting a clear, technically supported explanation of the scalability claim and its limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- backend, cloud, databases
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100