Our ongoing journey from REST to GraphQL on Android vol. 2

Here is the story of an ongoing migration... and what a migration! This journey moving from our REST API to a GraphQL one is a long run with much coordination across all tech teams.

This return of experience will focus on how we are dealing with this transition on Android where Retrofit coexists with Apollo, how we synchronized with backend teams to keep our GraphQL schemas up-to-date or how we are dealing with our authentication stack with Apollo Kotlin, or the issues we faced and much more.

Buckle up! Relax! The journey is now continuing 🚜

Transcript

1. 1 The Power of Conversation aircall.io Our ongoing journey from REST to GraphQL on Android Julien Salvi - Android GDE | Android @ Aircall Voxxed Days Luxembourg 󰏺 @JulienSalvi
2. 2 The Power of Conversation aircall.io Bonjour ! Julien Salvi Lead Android Engineer @ Android GDE “Android dev in shorts!” @JulienSalvi
3. 3 The Power of Conversation aircall.io Intro & context GraphQL and Apollo Kotlin REX: GraphQL migration Conclusion & Resources Summary
4. 4 The Power of Conversation aircall.io Introduction and context
5. 5 The Power of Conversation aircall.io “ ” What’s GraphQL?
6. 6 The Power of Conversation aircall.io Efficient data retrieval What’s GraphQL? 1 2 3 Single endpoint simplicity Strong typing and introspection GraphQL optimizes data fetching by allowing clients to specify their exact data requirements, eliminating over-fetching and under-fetching. GraphQL simplifies client-server interactions by using a single endpoint, reducing round trips and streamlining communication. GraphQL strong typing system ensures clarity in data exchange. Introspection capabilities enable powerful tools and automatic API documentation. “GraphQL is an open-source query language and runtime that provides an efficient and flexible approach to data fetching and manipulation. It was developed by Facebook and later open-sourced”
7. 7 The Power of Conversation aircall.io “ ” Why GraphQL at Aircall?
8. 8 The Power of Conversation aircall.io Why REST to GraphQL? Efficiency and data aggregation The need for efficient microservice communication and a data aggregator point. Scaling of REST API Wanted to break the REST API into microservices. It was not modular enough and has scaling issues. Minimum disruption Due to Internal usage of our REST APIs, we pushed us to take advantage of Graphql with minimum disruption to our customers. Serverless alternative Desire to create a serverless alternative API from the existing monolith REST interface.
9. 9 The Power of Conversation aircall.io Key points for GraphQL Data aggregation Clients can fetch multiple resources in a single request, reducing the number of network round trips. Efficient data loading GraphQL allows clients to request only the data they need, minimizing over-fetching and under-fetching. Strong typing GraphQL's type system ensures clear communication between clients and servers, reducing errors and providing reliable data validation. Federated GraphQL APIs Enables independent development, deployment, and scaling of individual services, resulting in improved maintainability and scalability of the system. Real time communication GraphQL provide a way to establish a persistent connection between the client and the server, enabling efficient and scalable real-time updates without the need for constant polling. Reduced latency GraphQL supports batching multiple requests into a single round trip, reducing network latency and improving overall performance.
10. 10 The Power of Conversation aircall.io “ ” How we use GraphQL?
11. 11 The Power of Conversation aircall.io The tech under the hood • Our infra relies a lot on AWS so our GraphQL backend teams went for AppSync. • AppSync offers many capabilities like filtering, real-time or scalability and has a nice integration with ElasticSearch, DynamoDB or Cognito.
12. 12 The Power of Conversation aircall.io The tech under the hood • On the Android side, we are using the Apollo Kotlin library to manipulate the GraphQL API. • offers many advantages: ◦ Great interoperability with Kotlin code base (100% Kotlin) ◦ Model generation in Kotlin ◦ Multiplatform ◦ Queries, Mutations and Subscriptions ◦ Caching system ◦ AppSync and graphql-ws support ◦ Awesome community support 💚
13. 13 The Power of Conversation aircall.io GraphQL API journey 2020 2021 2022 2023 First GraphQL queries in production GraphQL API introduction Monolith transition + GraphQL migration (backend) Migration of REST endpoints to GraphQL in client apps New features with GraphQL API GraphQL API in clients apps
14. 14 The Power of Conversation aircall.io Now let’s see how we brought GraphQL to Android with Apollo 🚀
15. 15 The Power of Conversation aircall.io GraphQL and Apollo Kotlin +
16. 16 The Power of Conversation aircall.io “ ” How to setup Apollo Kotlin?
17. 17 The Power of Conversation aircall.io Apollo Kotlin setup • Let’s see how straightforward is it to setup Apollo Kotlin in your Android projects. • Let’s see how to deal with the GraphQL schema (our source of truth). • Let’s see how to make Queries, Mutations and Subscriptions. • Let’s see how the Apollo client can coexist with the Retrofit client.
18. 18 The Power of Conversation aircall.io
19. 19 The Power of Conversation aircall.io GraphQL schema
20. 20 The Power of Conversation aircall.io
21. 21 The Power of Conversation aircall.io
22. 22 The Power of Conversation aircall.io
23. 23 The Power of Conversation aircall.io
24. 24 The Power of Conversation aircall.io 💡Pro tip IntelliJ • Take advantage of the GraphQL plugin by Jim Kynde Meyer to have the autocompletion/deeplink when writing your queries but… https://plugins.jetbrains.com/plugin/8097-graphql Add the following graphql.config.yml at the root:
25. 25 The Power of Conversation aircall.io 💡Pro tip IntelliJ • … There is another one! GraphQL plugin by Apollo 🚀 https://plugins.jetbrains.com/plugin/8097-graphql Add the following graphql.config.yml at the root:
26. 26 The Power of Conversation aircall.io Apollo client setup
27. 27 The Power of Conversation aircall.io GraphQL requests
28. 28 The Power of Conversation aircall.io Your GraphQL API is now ready to go in your Android app 🚀
29. 29 The Power of Conversation aircall.io REX: GraphQL migration 🔬 󰳘
30. 30 The Power of Conversation aircall.io “ ” Apollo 💚 Kotlin
31. 31 The Power of Conversation aircall.io Apollo 💚 Kotlin • Apollo is 100% Kotlin and multiplatform. • It has a great support for coroutines and Kotlin flows. • Generates Kotlin code from the schema (data classes for models and Query/Mutations)
32. 32 The Power of Conversation aircall.io
33. 33 The Power of Conversation aircall.io
34. 34 The Power of Conversation aircall.io “ ” Cross-team communication
35. 35 The Power of Conversation aircall.io Cross-team communication • It’s important to always communicate with your backend teams to avoid surprises on the front side • Have a backend-for-frontend (BFF) approach to expose what really matter to the front apps • Participate in the entity modeling, the construction of the queries/mutations. By doing so, everyone will be at the same page!
36. 36 The Power of Conversation aircall.io “ ” Beware the timeout
37. 37 The Power of Conversation aircall.io Beware the timeout • If you set a timeout for your REST API, DON’T use the same one for your GraphQL API. • Sync with your backend/client teams to identify the best timeout to pass to your GraphQL client • If you’re using OkHttp, DON’T reuse the same OkClient for your REST and GraphQL API.
38. 38 The Power of Conversation aircall.io “ ” Lazy loading
39. 39 The Power of Conversation aircall.io Lazy loading • When only a part of your app or a feature (eg. under a feature flag) is using the GraphQL API, use the lazy loading when injecting your client. • Dagger/Hilt exposed a Lazy interface to defer the resource loading.
40. 40 The Power of Conversation aircall.io “ ” Monitoring
41. 41 The Power of Conversation aircall.io https://github.com/ChuckerTeam/chucker Monitoring • In your develop or prod env. always monitor your requests. • Take advantage of the OkHttp Interceptor to monitor queries and mutation. • ⚙ Use Chucker tool in dev mode to monitor your requests • 👀 Check Nicola Corti’s talk about Chucker 4.0 at droidcon Berlin
42. 42 The Power of Conversation aircall.io Monitoring demo!
43. 43 The Power of Conversation aircall.io “ ” Nested queries Great power comes with great responsibilities 🦸
44. 44 The Power of Conversation aircall.io Nested queries • GraphQL offers many capabilities and one of them is the support of nested queries. • This is pretty efficient when aggregating multiple data at once. • ⚠ But the response time might increase a lot. Always monitor! • 🤝 Sync with your backend teams to find the best solution
45. 45 The Power of Conversation aircall.io Nested queries
46. 46 The Power of Conversation aircall.io 7-10s query 😱
47. 47 The Power of Conversation aircall.io Optimized query 😎
48. 48 The Power of Conversation aircall.io “ ” Subscriptions are cool… but aren’t easy! Especially with AppSync 😅
49. 49 The Power of Conversation aircall.io Subscriptions • Subscriptions are long-lasting operation which can maintain an open connection (mainly a WebSocket). • Data is pushed to the socket and listened on the client side. • Keeping the connection alive isn’t easy! • … and things might get a bit more complicated with AppSync 😅 • #SpoilerAlert: We had to build our own AppSyncProtol to better handle the token refresh.
50. 50 The Power of Conversation aircall.io How is this exception triggered? 🤔
51. 51 The Power of Conversation aircall.io
52. 52 The Power of Conversation aircall.io Subscriptions While investigating a socket disconnection issue with Apollo and AppSync subs, we saw an opened issue on their repository 👀
53. 53 The Power of Conversation aircall.io Auth has to be passed in the webSocket Url
54. 54 The Power of Conversation aircall.io With this method only resetting the client could do the trick 😣
55. 55 The Power of Conversation aircall.io Using a lambda will help us resetting the URL without resetting the client 😃
56. 56 The Power of Conversation aircall.io Subscriptions But no ongoing develop for that feature 🥲 So let’s contribute to Apollo Kotlin 🚀
57. 57 The Power of Conversation aircall.io “ ” Error handling
58. 58 The Power of Conversation aircall.io Error handling • Error handling with GraphQL is quite different from a REST API • Errors can be exposed in the Query/Mutation, be directly accessible in the ApolloResponse class or an Exception can be thrown 🥲 • ApolloResponse exposed a list of potential errors. • So multiple source of truth and error parsing…
59. 59 The Power of Conversation aircall.io
60. 60 The Power of Conversation aircall.io Work in progress 🚧
61. 61 The Power of Conversation aircall.io With Apollo 4.x But we improved the thing 😀
62. 62 The Power of Conversation aircall.io
63. 63 The Power of Conversation aircall.io
64. 64 The Power of Conversation aircall.io
65. 65 The Power of Conversation aircall.io “ ” Schema automation
66. 66 The Power of Conversation aircall.io Schema automation • At some point you will ne need to automate the GraphQL schema update. • More development on the backend side, more updates on the client side. • When working with multiple flavors this will be highly recommended! • Let’s see how we managed that with our CI.
67. 67 The Power of Conversation aircall.io Schema automation
68. 68 The Power of Conversation aircall.io Schema automation
69. 69 The Power of Conversation aircall.io Schema automation • When the CI has passed successfully we can merge it to develop branch. • If the CI failed, we checkout and fix branch. • If we can’t fix the update, we cancel the MR and sync with the backend teams.
70. 70 The Power of Conversation aircall.io Multiple flavors • When you have multiple flavors (eg. staging/prod or white labels…), you may have multiple schemas to maintain. • This will lead to multiple updates and potentially be more error-prone . • ⚠ More maintenance when dealing with multiple flavors.
71. 71 The Power of Conversation aircall.io “ ” Apollo issue? Apollo community 💚💪
72. 72 The Power of Conversation aircall.io Apollo Community 💚 • The community around Apollo GraphQL is amazing! • Apollo Kotlin is an open-source project . • Maintainers are very active and very helpful when you have a question or an issue. • Open an issue on GitHub or ask a question in the Kotlin slack 🚀 • Many good features to come with Apollo 4.0.0 🤩
73. 73 The Power of Conversation aircall.io Conclusion and Resources
74. 74 The Power of Conversation aircall.io Key takeaways Why it was the right move • Apollo Kotlin 🚀 • Easy integration • Coroutine/Flow support • Strong typing and contract with the API • Combined queries • Apollo community 💚 • Apollo maintainers 💚 Areas to watch • Collaborate/speak with your backend teams. • Error handling. • Subscriptions aren’t always reliable. • Apollo AppSync support.
75. 75 The Power of Conversation aircall.io GraphQL documentation https://graphql.org/ Apollo Kotlin https://www.apollographql.com/docs/kotlin/ Apollo Kotlin repository https://github.com/apollographql/apollo-kotlin Apollo GraphQL Summit videos https://www.apollographql.com/events/virtual-event/graphql-summit/ AWS AppSync https://aws.amazon.com/appsync/ AppSync Android SDK https://docs.amplify.aws/sdk/api/graphql/q/platform/android/ https://github.com/awslabs/aws-mobile-appsync-sdk-android Resources
76. 76 The Power of Conversation aircall.io Thank you! Have fun with GraphQL 😃 Julien Salvi - Android GDE | Android @ Aircall Voxxed Days Luxembourg 󰏺 @JulienSalvi