Few interesting ideas from AWS Builders Library
- design APIs to be safe for retries or idempotent for resiliency
- shuffle sharding to distribute load as system scales
- Amazon’s approach to failing successfully.
Toyota’s Five-why’s approach to root cause a problem – is good but not enough to find all other root causes that might also cause a problem.
Couple great talks on serverless
Smithy is an Apache-2.0 licensed, protocol-agnostic IDL for defining APIs, generating clients, servers and documentation. https://github.com/awslabs/smithy