Skip to content

/ guide

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Discussion: Architecture page and sub-sections #27

Open
rupakg opened this issue Jun 15, 2017 · 2 comments
Open

Discussion: Architecture page and sub-sections #27

rupakg opened this issue Jun 15, 2017 · 2 comments

Comments

@rupakg
Copy link
Contributor

@rupakg rupakg commented Jun 15, 2017 •
edited

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 rupakg added this to Icebox in Guide Jun 16, 2017
@mthenw
Copy link

@mthenw mthenw commented Jul 18, 2017

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 rupakg changed the title Content Contribution: Architecture page Discussion: Architecture page and sub-sections Aug 2, 2017
@rupakg
Copy link
Contributor Author

@rupakg rupakg commented Aug 2, 2017

@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 rupakg removed this from Icebox in Guide Aug 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@rupakg @mthenw
You can’t perform that action at this time.