Discussion: Architecture page and sub-sections

[serverless]

Discussion: Architecture page and sub-sections

[mthenw]

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]

@mthenw Breaking this issue into 4 separate content contribution issues. Renaming this one for preserving discussion.

Architecture (Introduction)

Moved to issue #55

The Serverless Architectural Pattern

Moved to Issue #52

Partitioning Logic

Moved to Issue #53

Event-Driven Architecture

Moved to Issue #54