The document discusses serverless architectures, specifically using AWS AppSync and GraphQL. It highlights the advantages, such as quick implementation and reduced server maintenance, alongside disadvantages including potential DynamoDB costs and steep learning curves. The author shares personal experiences and recommends alternatives like Prisma.

1. Serverless GraphQL
AWS AppSync

2. Jose Luis Fonseca
@joselfonseca
joselfonseca
https://josefonseca.me

3. Serverless
GraphQL

4. Serverless

5. Serverless architectures are application
designs that incorporate third-party
“Backend as a Service” (BaaS) services, and/
or that include custom code run in managed,
ephemeral containers on a “Functions as a
Service” (FaaS) platform.
Serverless

6. Serverless architectures are application
designs that incorporate third-party
“Backend as a Service” (BaaS) services, and/
or that include custom code run in managed,
ephemeral containers on a “Functions as a
Service” (FaaS) platform.
Serverless

7. https://martinfowler.com/articles/serverless.html
Serverless

8. GraphQL

9. GraphQL
Un lenguaje de consulta para APIs
Modelamiento tipado para definición de datos
Server-side Runtime para ejecutar consultas
https://graphql.org/learn/

10. GraphQL
https://graphql.org/learn/
schema.graphql

11. GraphQL
https://graphql.org/learn/

12. GraphQL
https://graphql.org/learn/

13. GraphQL
https://graphql.org/learn/

14. GraphQL
https://graphql.org/learn/

15. GraphQL
https://graphql.org/learn/

16. https://graphql.org/learn/

17. https://graphql.org/learn/
GraphQL
https://labs.getninjas.com.br/sharing-data-in-a-microservices-architecture-using-
graphql-97db59357602

18. AppSync

19. Demo

20. Como nos fue?

21. Como nos fue?
Pros:
- Implementación rápida
- Automatización de despliegue de entornos con CloudFormation.
- No manutención de servidores, redes, VPS ETC.
- Facilidad de cambio (AWS Lambda)

22. Como nos fue?
Cons:
- DynamoDB puede ser costoso y lento.
- Curva de aprendizaje (Resolvers Mapping Templates)
- Autenticación sin Cognito puede ser compleja y rara.
- Editor en linea se pone MUY LENTO con un schema grande
- Log de errores es muy complicado de leer
- Muy fácil caer en N+1
- Estados RAROS con nuevos deploys

23. Alternativas?
https://www.prisma.io

24. Gracias!