mthenw
commented
6 years ago Notes that I took while chatting with @rupakg
Target audience
A-level, C-level developers, devops
Introduction
- SOA -> microservices -> functions (serverless)
- serverless is like microservices but more granular
- serverless architecture: FaaS for compute, BaaS (backend-as-a-service) for everything else (DB, search, cache, CDN)
How serverless architecture looks like?
- serverless architectures are opinionated microservices architectures
- different serverless arch:
- greenfield - the whole system in functions
- adding features to a legacy system with functions (communication via SDK faster, or API Gateway endpoint - latency issue)
Challenges
- cold start
- API Gateway latency
- invocation limit
- distributed tracing
- centralized logging
Migration
- from traditional SOA architecture
- from microservices architecture
- grouping function is good (they can use the same DB)
- taking out functionalities from the existing system
Link to presentation when I cover some of the stuff from here: https://speakerdeck.com/mthenw/the-state-of-serverless-1
rupakg
Description
Discussion around content for the Architecture section of the guide.
Details:
Some suggested ideas and guidance for content in this section:
Architecture
A Look Back (Issue #55)
The Serverless Architecture (Issue #54)
Patterns for Partitioning Code (Issue #53)