BrikL's GraphQL journey started in 2016 with constantly changing business requirements towards finding the product market fit. The talk will share some insights on the journey and lessons learnt of a startup using GraphQL to enable high development velocity and how BrikL is using GraphQL today.
3. Tobias Meixner
3
▪ Born in Berlin
(born before it was cool)
▪ In Asia for over 6 years
▪ Based in Bangkok
& Guangzhou
▪ Co-Founder & CTO @
▪ @MeixnerTobias
13. About BrikL
13
▪ 2D & 3D
Design studio
▪ E-commerce
Platform for
Custom-Made
Products
▪ www.brikl.io
14. Why GraphQL
14
▪ Pure focus on Frontend development
▫ MVP-style / UI-Driven development
▪ GraphQL Schema as major constant in our
development
▪ GraphQL Schema as discussion base
between project shareholders
15. MVP (2016)
15
▪ React
▪ Redux
▪ graphql-js
▪ AWS Lambda (NodeJS)
▪ Amazon DynamoDB
Based on:
serverless/serverless-graphql
16. v1 (2017)
16
▪ React
▪ Redux Apollo Client
▪ graphql-js Apollo Server
▪ AWS Lambda (NodeJS)
▪ Amazon DynamoDB
19. Architecture
19
▪ Serverless from Day 1
▪ Managed Services where possible
▪ GraphQL as thin layer
▪ DynamoDB to
▫ Store “State”
▫ Emit events to streams
▫ Similar to Hasura 3factor app
21. Gatsby
21
▪ Source data from GraphQL
▪ Generate storefront pages
▪ Source data based on
selected store integrations
▫ Instagram, …
▪ Future > Content Mesh
22. Apollo Client
22
▪ Query, Mutation components
▪ In-Memory-Cache
▪ Link Context > JWT
▪ Error link > Sentry
▪ HTTP Link > CDN vs POST
▪ SSR in Gatsby
23. Apollo Server
23
▪ Apollo Server Lambda
▪ Apollo Engine
▪ Context > User, Config
▪ Cache Control > CDN
▪ graphql-shield > Authz
▪ graphql-tools > make Schema