Mutating Meetup with GraphQL

@brwngrldev Mutating with GraphQL @brwngrldev

@brwngrldev

@brwngrldev How old is Meetup? A 21 years old B
12 years old C 17 years old

@brwngrldev A 21 years old

@brwngrldev

@brwngrldev 01 Key challenges we’ve faced 03 02 Poor architecture
setup Insufficient to no caching Steep learning curve

@brwngrldev 01 Poor architecture setup

@brwngrldev What is the primary issue here?

@brwngrldev 01 02 03 04 05

@brwngrldev 01 02 03 04 05 All of the above

@brwngrldev How we’re fixing this simplifying our architecture

@brwngrldev

@brwngrldev The primary GraphQL API

@brwngrldev

@brwngrldev What SHOULD we do?

@brwngrldev $29k savings each month on AWS bill Get rid
of the middle-man We’ve seen increased performance and lower costs

@brwngrldev

@brwngrldev W.W.L. what we’ve learned

@brwngrldev “There are only two hard things in Computer Science:
_____ _____ and naming things”

@brwngrldev “There are only two hard things in Computer Science:
cache invalidation and naming things”

@brwngrldev 02 Insufficient to no caching

@brwngrldev Adding appropriate caching at each layer Hitting the database
for each request is not ideal. Caching helps to reduce the database I/O from: aws.amazon.com/aws-cost-management/aws-cost-explorer/features

@brwngrldev

@brwngrldev // Loaders.java register( IS_FEATURED_EVENT, newMappedDataLoader( isFeaturedEventLoader(), this.<Integer, Boolean>cacheOptions( IS_FEATURED_EVENT,
Duration.ofHours(1), Boolean.class ) ) )

@brwngrldev request member data loader group data loader

@brwngrldev request promise #1 promise #2 promise #n member data
loader group data loader

@brwngrldev request promise #1 promise #2 promise #n data data
data member data loader group data loader

@brwngrldev Steady decrease in read operations as a result

@brwngrldev

@brwngrldev Caching at each appropriate layer Apollo client caching, cache-control
headers, CDN caching, etc.

@brwngrldev

@brwngrldev Is it CACHED?

@brwngrldev query member($id: ID!) { member(id: $id) { __typename id
name email } } 01

name email } } 01 02 query member($id: ID!) { member(id: $id) { __typename id name } }

name email city } } 03

@brwngrldev

@brwngrldev W.W.L. what we’ve learned

@brwngrldev 03 Steep learning curve

@brwngrldev Caching won’t work if the queries and mutations aren’t
set up right Wait, shouldn’t I know about this?!

@brwngrldev

@brwngrldev Reducing duplicate data in the cache // Apollo Kotlin
extend type Query @ fi eldPolicy(forField: "group", keyArgs: "id") // Apollo React group: { read(_, { args, toReference }) { return toReference({ __typename: 'Group', id: args.id }); } }

@brwngrldev

@brwngrldev What DID they KNOW?

@brwngrldev What WOULD you do?

@brwngrldev

@brwngrldev Help others to be self-sufficient Engineers have access to
the schema on Hive

@brwngrldev “Each one, teach one”

@brwngrldev Automate what you can add_tags: needs: fi lterChanges steps:
- name: Add GraphQL label to PR if: ${{ needs. fi lterChanges.outputs.graphql == 'true' }} run: | PAYLOAD='{"labels":["graphql"]}' LABEL_URL=${{github.event.pull_request.issue_url}}/labels curl … Use GitHub Actions to label a PR as including GraphQL changes

@brwngrldev

Mutating Meetup with GraphQL

Mutating Meetup with GraphQL

More Decks by Annyce D.

Other Decks in Technology

Featured

Transcript