DEV Community

Discussion on: Solutions Architect Tips - Decoding the AWS Serverless Design Principles

Collapse
 
allenheltondev profile image
Allen Helton

I think that comes down to governance. Make sure in your PRs people aren't building "lambdaliths"
That is a popular model I've seen, using something like express to essentially turn a lambda into a controller. According to the AWS best practices though, I don't think that's the recommended method.

Collapse
 
raphael_jambalos profile image
Raphael Jambalos

Agreed! but its so easy to regress into a monolith since the Serverless Framework / SAM allows the developer too much leeway.

Recently, I discovered serverless stack (serverless-stack.com/) as a kind of more mature framework that imposes some sort of convention to force the kind of separation, but even this has a tendency to grow several small Lambdaliths inside the repository.

What tools can you advise aside from Serverless Stack to do this? I cant seem to find any for Python...