Keynote: GraphQL In The House
summary
Office of the Clerk modernizes a 30-year legislative system by migrating LIMBS from a mainframe-backed legacy DB to a Red Hat Linux-hosted relational database, a microservice business logic layer, and a React/Apollo SPA front end; GraphQL sits on top via Hasura as API server with views-only DB access and mutations funneled through a business logic layer, implementing a CQRS loop and nightly syncs to legacy data, and the platform substantially reduces API churn while meeting strict correctness and performance needs.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 2:07Legacy system overview
- 5:03Why GraphQL was chosen
- 7:10System architecture design
- 9:22Long-term data goals
- 12:12Benefits and simplicity
- 16:29Conclusion and Q&A
related talks
14mKeynote: GraphQL in the AI Era
32mModernize development and activate legacy data with GraphQL
28mModernizing App Development: Planet-scale GraphQL & Distributed SQL
55mUsing GraphQL in Danish Government Systems
23mGraphQL, Public Sector
19mBringing GraphQL to the Enterprise: When IBM met Apollo
23mAugmenting a Legacy REST API with GraphQL
39mArchitecture of scalable and resilient NodeJS apps with GraphQL & event-driven serverless
