1
0
mirror of synced 2025-12-19 18:11:23 -05:00

fix: small errors in rfc docs (#2217)

(ignore)
This commit is contained in:
0xflotus
2021-04-14 17:40:21 +02:00
committed by GitHub
parent 03ebcb911d
commit fc216c283d
2 changed files with 2 additions and 2 deletions

View File

@@ -316,7 +316,7 @@ GraphQL is a great technology, but it's not great as the backbone for apps that
Primarily because GraphQL is not scalable when deployed to serverless platforms like Zeit or Netlify. It's not scalable because all of your resolver code is stuffed into a single Lambda causing you to quickly run into cold start issues and max code size issues.
Anyone deploying a sizable GraphQL API via serverless Lambda functions does so by splitting the graph into many small Lamba functions, each of which is responsible for discrete set of types. Then you have a separate gateway like Apollo Federation or GraphQL Mesh to stitch the entire schema back together again.
Anyone deploying a sizable GraphQL API via serverless Lambda functions does so by splitting the graph into many small Lambda functions, each of which is responsible for discrete set of types. Then you have a separate gateway like Apollo Federation or GraphQL Mesh to stitch the entire schema back together again.
Other reasons include:

View File

@@ -107,7 +107,7 @@ Blitz is defining a standard file structure to answer the age old question of "H
Contains all your core application code.
- The file structure nested inside `app` can be anything you want, but we reccomend the following:
- The file structure nested inside `app` can be anything you want, but we recommend the following:
- Typically you will have two types of "container" directories inside `app` that can be nested or combined any way you want:
- **entity** directories like `projects/` and `tasks/`
- **context** directories like `marketing/` or `admin/`.