title: Codebase Organisation for Microservice using AWS Lambda
body: <p>Several different endpoints for a resource can exposed from <code>API Gateway</code> (e.g. - <code>/customer</code>), with different serverless functions deployed in <code>AWS Lambda</code> supporting <code>GET/POST/PUT/DELETE</code> operations on the resource. For each serverless function it has to be deployed separately in <code>AWS Lambda</code>. Now since they all work on a same <code>backend/data-model/underlying resource</code>, what should be the ideal structure for codebase for these serverless functions? Separate codebase for each endpoint, or one codebase with different handler to handle diff functions? What would be the Pro's and Cons for each?</p>