Serverless Best Practices

Each function should do only one thing

Functions don’t call other functions

Use as few libraries in your functions as possible (preferably zero)

Avoid using connection based services e.g. RDBMS

One function per route (if using HTTP)

Learn to use messages and queues (async FTW)

Data flows, not data lakes

Just coding for scale is a mistake, you have to consider how it scales

Conclusion

ServerlessDays CoFounder (Jeff), ex AWS Serverless Snr DA, experienced CTO/Interim, Startups, Entrepreneur, Techie, Geek and Christian

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Adaptive Throttling of Indexing for Improved Query Responsiveness

Test-Driven Development

Addressables in Unity: bundles and catalogs issues

How to create a decorator for checking groups in Django

CS373 Spring 2033: Dani Amir - Final Entry

LeetCode][python3]Day24. LRU Cache (30-Day LeetCoding Challenge)

Web3 Builders: ChainSafe

Android App Architecture Ground Up

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Paul Johnston

Paul Johnston

ServerlessDays CoFounder (Jeff), ex AWS Serverless Snr DA, experienced CTO/Interim, Startups, Entrepreneur, Techie, Geek and Christian

More from Medium

Increase AWS Lambda Speed and Save Money

All you need to know about DynamoDB Keys

How to use V2 Aurora Serverless Database with CDK v2.20.0 library

Unlocking new potentials in AWS Lambda with larger ephemeral storage