The document discusses the implementation of GraphQL on ASP.NET Core, highlighting its benefits such as eliminating over- or under-fetching, simplicity, and real-time capabilities. It contrasts GraphQL with REST and outlines its operations, including queries, mutations, and subscriptions, as well as schema stitching for microservices. Various demos and links to resources such as GitHub and websites for further learning about Hot Chocolate and GraphQL are provided.

1. GraphQL on ASP.NET Core
WITH

2. Who are we?

3. Who is this for?Who is this for?

4. demo.chillicream.com

6. query {
me {
name
age
}
}
{
"me": {
"name": "Foo",
"age": 99
}
}

7. GET
https://webservices.amazon.com/onca/xml?
Service=AWSECommerceService&
AWSAccessKeyId=mY-Sup3r-s3cr3!-k3y&
AssociateTag=12345&
Operation=ItemLookup&
ItemId=0316067938&
ResponseGroup=Reviews&
TruncateReviewsAt=256&
IncludeReviewsSummary=False&
Version=2013-08-01&
Timestamp=[YYYY-MM-DDThh:mm:ssZ]&
Signature=[Request Signature]

10. What is GraphQL?

11. GraphQL
No over- or under-fetching
One Request
Type System
No versioning
Simplicity
One Endpoint
Documentation
Real-time
Predictability

12. What GraphQL is not:
• Graph database query language
• Solution for binary streams
• Facebooks version of OData
• Bound to a specific data source
• Limited to HTTP
• Limited to the JavaScript world
• A good solution for a health
check endpoint.

13. REST GraphQL
Shared Definition No Yes
Conceptual Model Resources Graphs
Organization Federated Centralized
Related Ops Yes No
Introspection No Yes
Data Typing Weak Strong
Real-Time No Yes

14. GraphQL Operations:
• Query = Read
• Mutation = Write
• Subscription = Events

15. Demo

16. Resolvers and Pipelines

17. Demo

19. query {
me {
friends {
friends {
friends {
name
}
}
}
}
}

20. Demo

21. Scaling Your Graph

22. query {
me {
name
age
}
}

23. query {
me {
name
age
friends {
name
age
}
}
}

24. query {
me {
friends {
friends {
friends {
name
}
}
}
}
}

25. query {
me {
name
stories(first: 10) {
... Content
}
}
}

26. query {
me {
name
stories(first: 10000) {
... Content
}
}
}

28. type User {
stories(first: PaginationAmount): [Story!]!
}
SchemaBuilder.New()
.AddType(new PaginationAmountType(50))
...
.Create();
type User {
stories(first: Int): [Story!]!
}

29. type User {
stories(first: PaginationAmount): [Story!]!
@cost(complexity: 5)
}

30. type User {
stories(first: PaginationAmount): [Story!]!
@cost(complexity: 5 multipliers:[first])
}

31. 1
1 50
me
Stories(first: 10)name

32. 1
1 5000
me
Stories(first: 1000)name

33. Demo

34. Persisted Queries

35. GraphQL Client GraphQL Server
High Bandwidth Usage
{
"query" : <query>
}

36. GraphQL Client GraphQL Server
Unrestricted Query Execution
{
"query" : <query>
}

37. GraphQL Client GraphQL Server
Low Bandwidth Usage
{
“id” : “W5IYenw==”
}
Middleware

38. GraphQL Client GraphQL Server
Restricted Query Execution
{
“id” : “W5IYenw==”
}
Middleware

39. Demo

40. Testing Your Schema

41. Demo

42. How can we do microservices with
that?

43. What is
schema
stitching?

44. The capability to merge multiple
GraphQL schemas into one
schema.

45. Hot Chocolate Gateway
Hot Chocolate GraphQL
Mongo DBRaven DB
Abritray REST Endpoint
{REST}
SQL Server
query {
me {
messages {
# Hot Chocolate GraphQL
text
# Apollo Server
createdBy {
name
}
# Abritray REST Endpoint
views
likes
replies
}
}
}
One GraphQL Query
Apollo GraphQL

46. Demo

48. Where do you find us?
https://github.com/ChilliCream
https://chillicream.com
https://hotchocolate.io
https://twitter.com/Chilli_Cream