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

Secondary IS as a Federated IDP for WSO2 IS

Devengers | Building Production Grade Serverless Applications | DevRel

Definition of computer storage devices

Terkehh Airdrop round 2 (Deposit confirmation) ★★★★★

Dear Oly Racers,

I will create 3d cartoon animation, 3d character animation, 3d character design

🧱 Setup Web Server inside Docker Container Using Ansible Playbook

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

Remake-Serverless — use Remake without a server

Cloudflare Workers vs AWS Lambda: Detailed Comparison

Unleashing the power of serverless for solo developers

Unlocking new potentials in AWS Lambda with larger ephemeral storage