guide icon indicating copy to clipboard operation
guide copied to clipboard

Published 20 hours ago • verified publisher icon serverless

Discussion: Architecture page and sub-sections

Open rupakg opened this issue 7 years ago • 2 comments

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)

  • n-Tier Architecture
  • SOA
  • Microservices Architecture

The Serverless Architecture (Issue #54)

  • Why do we need a new architectural pattern?
  • Functions as a Service (FaaS)
  • How do we get there?
    • Need for agile development lifecycles
    • Need for independent teams working in parallel
    • Focus on building than managing infrastructure

Patterns for Partitioning Code (Issue #53)

  • Nanoservices
  • Microservices
  • Monolithic
  • GraphQL

rupakg avatar Jun 15 '17 23:06 rupakg

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

mthenw avatar Jul 18 '17 10:07 mthenw

@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

rupakg avatar Aug 02 '17 17:08 rupakg