Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Deploying GraphQL in a Serverless Context - React Rally 2016

Deploying GraphQL in a Serverless Context - React Rally 2016

Kevin Old

August 25, 2016
Tweet

More Decks by Kevin Old

Other Decks in Technology

Transcript

  1. What is a Serverless architecture? How GraphQL fits into a

    Serverless architecture How to get started with Serverless + GraphQL Immediate use cases Pros and Cons Agenda
  2. Write single-purpose stateless functions Design push-based, event-driven pipelines Create thicker,

    more powerful front ends Embrace third party services Use a compute service to execute code on demand Principles of a Serverless Architecture
  3. Click "Create a Lambda function" Choose a Blueprint function Configure

    how it is triggered (API Gateway, DynamoDB, CloudWatch, etc.) Configure the function Runtime (Node.js 4.3) Memory Timeout Lambda function code (in WYSIWYG editor) Handler path inside container Role creation Policy creation VPC access
  4. + =

  5. 101 $ npm install -g serverless@beta $ serverless create -t

    aws-nodejs $ serverless deploy $ serverless remove
  6. Pros No longer managing servers Not running server(s) 24 /

    7 Scale instantly Serverless, Apex, etc. AWS, Google, Microsoft, IBM solutions Pay only for what you use
  7. Marketing site (S3) + Form Mobile backends Background Jobs (Image

    resize, log processing) CMS and low-bandwidth BFF's (Backend's for Frontend’s) Any pre-compute stored (S3) for later retrieval Startups / Prototyping products Test, Dev and Staging environments Immediate Use Cases
  8. Server-rendered React Security/Compliant heavy apps Read-only API’s Anything with an

    SLA High throughput / availability Possible, but not a good fit?
  9. Cons Limited documentation/examples Latency Best practices are still being defined

    Security Offline development Serverless (v0.x stable, v1 beta), Apex, etc.