Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Rescuing legacy codebases with GraphQL

Rescuing legacy codebases with GraphQL

GraphQL is one of the hottest technologies of the past year or two. Still, very little is talked about GraphQL outside of the realm of front-end applications.

We used a different approach at IFTTT and applied GraphQL as an integration layer for different backends and client apps.

This talk goes beyond the basic configuration of a GraphQL endpoint with Rails. I’ll cover topics such ActiveRecord Query optimization, performance monitoring, batching and share some of the challenges we ran into while building a GraphQL API that serves over 10 thousand queries per minute.

Ivayr Farah Netto

May 22, 2017
Tweet

More Decks by Ivayr Farah Netto

Other Decks in Programming

Transcript

  1. Context • Millions of users • Billions of API calls

    every day • Website, iOS app, Android app
  2. Tech Stack (at the time) • Seasoned Rails 3 monolith

    app • APIs v1, v2, v3, dev_api… • Challenging to deploy/iterate/run tests • sole web dev
  3. GraphQL API ——— MonoRail ☁ A P I 
 G


    A
 T E
 W
 A Y Service A Service B Service C
  4. GraphQL API ——— MonoRail ⛈ A P I 
 G


    A
 T E
 W
 A Y Service A Service B Service C
  5. SELECT "recipes".* FROM “recipes" SELECT "ingredients".* FROM "ingredients" WHERE "ingredients"."recipe_id"

    = 1 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 1 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 2 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 3 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 4 SELECT "ingredients".* FROM "ingredients" WHERE "ingredients"."recipe_id" = 2 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 5 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 6 SELECT "ingredients".* FROM "ingredients" WHERE "ingredients"."recipe_id" = 3 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 7 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 8 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 9 SELECT "ingredients".* FROM "ingredients" WHERE "ingredients"."recipe_id" = 4 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 10 SELECT "vendors".* FROM "vendors" WHERE "vendors"."id" = 11
  6. SELECT "ingredients".* FROM "ingredients" WHERE "ingredients"."recipe_id" = 1 SELECT *

    FROM "vendors" WHERE "id" = 1 SELECT * FROM "vendors" WHERE "id" = 2 SELECT * FROM "vendors" WHERE "id" = 3 SELECT * FROM "vendors" WHERE "id" = 4
  7. query { recipes { title ingredients { name vendor }

    } } Recipe.all.includes({ ingredients: 'vendor' })
  8. SELECT "recipes".* FROM "recipes"
 SELECT "ingredients".* FROM “ingredients” WHERE “ingredients"."recipe_id"

    IN (1, 2, 3, 4) 
 SELECT "vendors".* FROM “vendors" WHERE “vendors"."id" IN (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
  9. # At the field level new_resolver = -> (obj, args,

    ctx) { name = [“GraphQL/field/#{type.name}.#{field.name}"] NewRelic.trace_execution_scoped(name) do old_resolver.call(obj, args, ctx) end } # At the query level NewRelic::Agent.set_transaction_name(query_name)