serverless / serverless/examples
Serverless for larger Applications [Suggestion needed]
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.5k
- Forks
- 4.4k
- Avg merge
- 2h 55m
- Merged PRs (30d)
- 3
Description
Hi All,
I've been working with serverless for around 1 year but the problem is that I didn't find a single concrete solution for implementing the serverless architecture for larger applications that are easy to manage, update, and highly recommended.
Problems
- I have some utility function files that I need to use in almost every function.
- There will be around 100 APIs.
Considering resources limitation in CloudFormation I come up with these following ideas.
Solutions
- Divide the whole app into multiple services and deploy (But how do I update the utility functions and classes, It should be in one directory)
- Should I use the Flask within a single function to handle multiple routes? (I don't know how this works with threshold or other things)
Any other idea would you suggest and why it’s good.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points to investigate. First clarify the intended architecture for large serverless applications, including shared utilities, service boundaries, and routing; done would require a concrete, agreed implementation scope rather than general suggestions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, flask
- Domain
- backend-api-design, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100