Web technologies are evolving blazingly fast and so it is AWS. Part of this evolution is GraphQL and the AWS team already took notice. In March 2019 AWS joined the GraphQL Foundation, double betting on the technology as an ingredient for great applications. Designing GraphQL API's for scale on AWS is a challenging and exciting process, in this talk, we will talk about some key learnings from my past two years and how to overcome several challenges of this process.

1. @bogdanned github.com/bogdanned
GraphQL @production on AWS
!1
🧙

2. @bogdanned github.com/bogdanned
– The Wikipedia
“In the context of computer programming, magic … it is
used to describe code that handles complex tasks while
hiding that complexity to present a simple interface. ”
!2

3. @bogdanned github.com/bogdanned
@production
!3
- critical user impact🤕
- limited replicability 🤐
- resilience && scalability$

4. @bogdanned github.com/bogdanned !4
- Schema Design @production
- System Design with Graphql

5. @bogdanned github.com/bogdanned !5
- Schema Design @production
- System Design with Graphql

6. @bogdanned github.com/bogdanned !6
- Superfluous Resolver Calls 😓

7. @bogdanned github.com/bogdanned !7

8. @bogdanned github.com/bogdanned !8

9. @bogdanned github.com/bogdanned !9
So should we dataload the whole thing?
Requests Saved = NP - NC 🤷

10. @bogdanned github.com/bogdanned !10
- Schema Design @production
- System Design with Graphql

11. @bogdanned github.com/bogdanned !11
- Schema Design @production
- System Design with Graphql

12. @bogdanned github.com/bogdanned
What does GraphQL implies for our systems?
!12

13. @bogdanned github.com/bogdanned !13
–The GraphQL Website
“GraphQL is a query language for your API, and a server-side runtime
for executing queries by using a type system you define for your data.”

14. @bogdanned github.com/bogdanned
–Johnny Appleseed
Under the hood …
!14
- The Api Gateway pattern
- The Enterprise Data Model pattern
- The Integration Database pattern
- The Backend for Front End pattern: BFFF

15. @bogdanned github.com/bogdanned
–Johnny Appleseed
Under the hood …
!15
- The Api Gateway pattern
- The Enterprise Data Model pattern
- The Integration Database pattern
- The Backend for Front End pattern: BFFF
🚦

16. @bogdanned github.com/bogdanned !16
- service client coupling
- too many round trips
- redundant edge functions

17. @bogdanned github.com/bogdanned !17

18. @bogdanned github.com/bogdanned !18
- reverse proxy
- gateway offloading
- request aggregation

19. @bogdanned github.com/bogdanned
- single point of failure 🙏
- vertical scaling
- horizontal scaling )
- release coupling
!19

20. @bogdanned github.com/bogdanned
–Johnny Appleseed
Under the hood …
!20
- The Api Gateway pattern
- The Enterprise Data Model pattern
- The Integration Database pattern
- The Backend for Front End pattern: BFFF
🗺

21. @bogdanned github.com/bogdanned !21
Apollo Federation
-separation of concerns
-distributed graph
-development tooling

22. @bogdanned github.com/bogdanned !22
-heterogeneity
-schema matching
-schema mapping
Federated Database

23. @bogdanned github.com/bogdanned
– Phil Calcado, Some thoughts on GraphQL vs. BFF 2019
“ .. it is hard for me to believe that you can combine the needs of
many different applications, owned by different teams, with different
users and use cases, in a single schema”
!23

24. @bogdanned github.com/bogdanned !24
😭
Which amount?

25. @bogdanned github.com/bogdanned
–Johnny Appleseed
Under the hood …
!25
- The Api Gateway pattern
- The Enterprise Data Model pattern
- The Integration Database pattern
- The Backend for Front End pattern: BFFF
,

26. @bogdanned github.com/bogdanned !26

27. @bogdanned github.com/bogdanned
Thank @you !
!27
🧙