dwyl/learn-aws-lambda

Should each Lambda function be created in a new repo?

Open

#42 opened on Jan 29, 2016

View on GitHub
 (26 comments) (17 reactions) (0 assignees)JavaScript (206 forks)batch import
help wantedquestion

Repository metrics

Stars
 (1,037 stars)
PR merge metrics
 (Avg merge 16m) (1 merged PR in 30d)

Description

Any thoughts on how we should organise our lambda functions?

Contributor guide

Research direction
Investigate common Lambda organization patterns such as monorepo vs multi repo, and consider team size, deployment frequency, and code sharing needs.
Tech stack
None
Domain
cloud
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80