Tradeoffs between leveraging FHIR REST APIs vs. GraphQL APIs

on YouTube ↗32m

" summary

Compares REST vs GraphQL for read-only, interactive FHIR use cases and reports a working GraphQL server built in Go with gqlgen and DynamoDB, using heavy code generation that forced a switch from explicit unions to a generic reference type to avoid compile bloat. Implements cursor pagination (GraphQL-style), a custom filter syntax inspired by Dgraph, and a small, opt-in set of search params; notes missing GraphQL-with-FHIR guidance, no robust mutations, introspection/logging tradeoffs, and practical parser compatibility workarounds.

AI-written summary · about

" chapters (13)

1. 0:00Introduction and context
2. 1:29Interactive vs bulk use cases
3. 3:18REST API overview and limitations
4. 7:11GraphQL API advantages
5. 10:22GraphQL API limitations
6. 12:32Implementation challenges
7. 18:10Adoption and parser issues
8. 20:59Custom API decisions
9. 24:48Summary of deviations
10. 26:37Hot take on search parameters
11. 27:38Mutations and write operations
12. 29:02Choosing REST vs GraphQL
13. 30:27Q&A

" related talks

• 27mA no nonsense GraphQL and REST comparisonPhil Sturgeon · RubyConf Colombia 2017
• 18mIs GraphQL the end of RESTstyle APIsJoakim Lundborg · Nordic APIs Platform Summit 2016
• 58mGraphQL -- Flexible APIs for Adaptive ClientsBrian Genisio · CodeMash 2018
• 23mAn Introduction to GraphQLNat Welch · SREcon19 Americas
• 40mGraphQL: A Case StudyBernd Schönbach · code.talks 2017
• 47mGraohql & GraphDefinitionGrahame Grieve · HL7 FHIR DevDays 2019 Redmond
• 51mGraphQL: advantages, challenges, and how to overcome themArnauld Desprets, Ivan Pryanichnikov · Apidays LIVE Paris 2020
• 31mGraphQL: how to make clients enjoy using your APITomasz Modrzyński · PyCon AU 2017