Should I create different git repository for different AWS lambda functions?

Question

There are some cons for using single repository for all my lambda functions of a project like:-

Size of deployment package becomes huge. So, when only 1 lambda is changed, entire package is recreated and deployed to AWS.

Also, different repositories for different lambdas can give us privilege of changing lambda code without affecting other lambdas, but it has its own cons.

So, what is the best design for coding in the AWS lambdas?

Gauranga Rathod · Accepted Answer · 2017-04-03 05:28:02Z

5

After some research, I found out.

You need to group relevant lambda functions for e.g 4 lambda functions for CRUD operations corresponding to a single resource should be in a single repository.

Lambda functions concerning with different resource or irrelevant functions should be in a different repository.

Reference: Serverless framework documentation.

answered Apr 3, 2017 at 5:28

Gauranga Rathod

3585 silver badges16 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Should I create different git repository for different AWS lambda functions?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related