"In a micro-service architecture, managing REST API surfaces can get out of control in a hurry. And on bigger teams, utter chaos is just one breaking change away. In this talk, we'll take a look at how IBM's Bluemix is leveraging GraphQL to unify dozens of independent services by consuming and normalizing their APIs — all while creating huge (~2.5x) performance improvements. We'll also look at how you can use this technique in companies of any size to create a better, more reliable data layer and improve the experience for both the customers using the platform AND the developers building the platform."

1. Tweet: @jlengtorf #APItrat
WHN RT
IN’T NOUGHXTNDING RT WITH GRAPHQL

·
Jaon Lengtorf
 @jlengtorf jaon.lengtorf@im.com
lide: git.io/vFvei

2. WHO I AM
uilding we thing ince 2003
enior developer / architect @ IM Cloud
Former workaholic
Current work­life alance advocate
Oeed with procee & e cienc

3. GRAPHQL I ON OF TH MOT
XCITING THING I’V WORKD
ON IN A LONG TIM

4. WHY GRAPHQL I XCITING:
Wrap exiting RT endpoint with minimal code
Reduce demand on API team to create aggregate
endpoint
Create a ingle ource of truth for data
nale mock repone and local development
Come with rower­aed tool for exploring data
and teting querie

5. THI PROMID
OLUTION TO A LOT
OF OUR PAIN

6. HOW IM CLOUD I UILT:
Node µ­ervice architecture
30+ µ­ervice team
ach µ­ervice (“plugin”) i a eparate codeae
Team control their own work ow

7. THI HA IT DOWNID:
Thing can change in 30+ direction at an given time
Front­end need data from multiple µ­ervice
Internal documentation & architecture i inconitent
Code can e wildl inconitent etween µ­ervice

8. GRAPHQL HA OLUTION:
Change are centralized in the GraphQL µ­ervice
Data acce happen through a ingle endpoint
Documentation i centralized and conitent
Cleaner eparation etween data and preentation

9. I WANTD TO TART UING IT IN
PRODUCTION IMMDIATLY

10. NOT VRYON WA ON OARD

11. THR AR COMPLICATION:
Who “own” the GraphQL µ­ervice?
How can team make independent change?
Can one ad commit take down the whole ervice?
Doen’t an extra laer make it harder to trace error?

12. W WANTD TH NFIT OF
GRAPHQL… UT COULD W
AFFORD TH TRAD OFF?

13. W NDD ANWR

14. CAN W...
1. Centralize data, ut let team keep control?
2. Deign an approach that improve error handling?
3. Make it o ea team want to witch?
4. uild a ervice that can handle IM’ cale?

15. CHALLNG #1:
CNTRALIZ DATA,
UT DCNTRALIZ
CONTROL

16. TH IDAL OLUTION:
ach team maintain their own GraphQL chema...
ut that chema i aggregated  a central µ­ervice.

17. IF THI WA GOING TO WORK, W
NDD A TANDARDIZD FORMAT
FOR HARING CHMA.

18. W CALL TH
DATA OURC

24. ACH DATA OURC I AN
INDPNDNT GITHU RPO,
WHICH MAN:
✅ No ottleneck
ach team commit and deplo code independentl.
✅ No lo of control
ach team own their data ource.
✅ No accidental orking
ach team’ code ha individual tet uite.

25. HOW DO W COMIN TH
DATA OURC?

30. CHALLNG #2:
IMPROV RROR
HANDLING

31. WHAT MAK AN RROR HLPFUL?
Clear decription of what went wrong
Clarit aout where the error occurred
GraphQL error v. underling data acce iue
Information to help with tracing ug
Unique ID hared on the client and erver ide

32. CLINT ID RROR IN DVLOPMNT

33. IN PRODUCTION, W CAN’T HOW OM DATA
Doc link ma e ehind our rewall
Target endpoint ma not e pulic

34. CLINT ID RROR IN PRODUCTION
docsLink and targetEndpoint are removed in production.

35. CLINT AND RVR RROR HAR A GUID
Error: Could not load the given xkcd comic
(178460c1-c8d7-42c2-ba0e-f617afb5d3fd)
Description: Could not load the given xkcd comic
Error Code: XKCDModel_Error
GraphQL Model: XKCDModel
Target Endpoint: https://xkcd.com/2000/info.0.json
Documentation: https://ibm.biz/gramps-data-source-tutorial
Data: {
"id": "2000"
}
Uing the GUID, we can nd the docsLink and targetEndpoint in the erver log.

36. THI MAN...
rror are normalized acro all data ource
upport ticket can directl reference detail in log
rror are clear and come with documentation
The ource of a given error i immediatel clear

37. IMPLMNTATION I OPTIONAL AND AY
import Express from 'express';
import bodyParser from 'body-parser';
import { graphqlExpress } from 'apollo-server-express';
import { grampsExpress } from '@gramps/gramps-express';
import schemaOne from '@gramps/data-source-one';
import schemaTwo from '@gramps/data-source-two';
const app = new Express();
app.use(bodyParser.json());
app.use(grampsExpress({ dataSources: [ schemaOne, schemaTwo ] }));
app.use('/graphql',
graphqlExpress(req => ({
schema: req.gramps.schema,
context: req.gramps.context,
+ formatError: req.gramps.formatError,
})),
);

38. CHALLNG #3:
MAK DVLOPMNT
O AY TAM
WANT TO U IT

39. IF W WANTD TAM TO
TART UING GRAPHQL, W
NDD IT TO  DAD IMPL
TO GT TARTD

40. W CRATD A DATA OURC
TARTR KIT:
trong tarting point for new data ource
tep­­tep tutorial for uilding a new data ource
Tet coverage tart at
Pre­con gured for Travi CI and Code Climate
githu.com/gramp­graphql/data­ource­ae

41. W UILT A CLI TO MAK DVLOPMNT AIR
$ gramps --live
============================================================
GrAMPS is running in live mode on port 8080
GraphiQL: http://localhost:8080/graphiql
============================================================

42. UT THR WA A NAG:
“How do we run a local intance of the GraphQL
µ­ervice if the data ource we’re developing i alread
intalled? Won’t the collide?”

43. TH OLUTION?
ALLOW LOCAL
DATA OURC
TO OVRRID
gramps --data-source-dir ./

44. UT ADD A WARNING
Clari ed text and updated link are coming ( )#36

45. ACTUALLY, ADD TWO WARNING
Clari ed text and updated link are coming ( )#36

46. CHALLNG #4:
UILD FOR
GLOAL CAL

47. W DIDN’T HAV TO DO MUCH
It turn out Apollo’ xpre erver jut work.

48. WHICH I PRTTY GRAT

49. OKAY, UR, UT HOW LONG DID
IT TAK TO GT GRAPHQL INTO
PRODUCTION?”

50. W TARTD WORKING ON TH
GRAPHQL µ­RVIC IN MAY

51. IT HIT PRODUCTION IN JULY

52. AFTR TH DUT TTLD,
W RALIZD TWO THING

53. #1
“Hol hit, if everone wrote their data ource uing
thi format, the dev communit could hare GraphQL
data ource a eail a we hare npm package.”

54. #2
“Thi might e ueful to other people.”

55. O W’R
RLAING IT UNDR
TH MIT LICN

56. GrAMP: GraphQL
Apollo Microervice
Pattern erver
INTRODUCING
GRAMPGraphQL Apollo Microervice Pattern erver
· githu.com/gramp­graphql/gramp­expre npmj.com/org/gramp

57. THANK!
Jaon Lengtorf
Follow me on Twitter: ·
·
 @jlengtorf jaon.lengtorf@im.com
githu.com/gramp­graphql/gramp­expre npmj.com/org/gramp

58. ROURC
1. GrAMP on GitHu
(http://githu.com/gramp­graphql)
2. GrAMP xpre Middleware
(http://githu.com/gramp­graphql/gramp­expre)
3. GrAMP Documentation
(http://gramp­graphql.githu.io/gramp­expre/)
4. How to uild GraphQL erver
(http://dev­log.apollodata.com/how­to­uild­graphql­erver­
87587591ded5)
5. GrAMP Data ource tarter Kit
(http://githu.com/gramp­graphql/data­ource­ae)
6. GrAMP Data ource Tutorial
(http://im.iz/gramp­data­ource­tutorial)
7. GrAMP on npm
(http://www.npmj.com/org/gramp)