GraphQL at Different - A case study (Presented at GraphQL Sydney Meetup)

Transcript

1. GraphQL at :Different A case study Matt Valley / Javascript (React, Node) consultant GraphQL Sydney meetup, 2020-04-16 Mattvalley.com linkedin.com/in/matthew-valley hi@mv.id.au @mattvalleycodes
2. :Different “Full-service residential property management for $100.”
3. The journey started with our founders helping their parents with their investment properties.
4. Oops! We’re live and people love the idea! Keep building new features!
6. Technical Debts Core & UI data stored next to each other Almost everything was nullable New tables to store 1-1 relationships JOINs here, there & everywhere! Lots of them! DB represents UI!
7. Technical Debts Endpoints tailored to one single use-case Data inconsistencies across the board Manual / Out-dated API documentation Unable to repurpose the endpoints
8. Goals Restructure the database A reusable, extendable and client-agnostic API Eventual transition rather than stop-the-world-and-rewrite-everything approach. An abstract layer on top of the database(s)
9. GraphQL It’s client-agnostic. Consumable by web apps, native-apps and back-end services. We can build a reusable graph of our data Can be an abstract layer on top of the databases. Comes with good tooling for documentation It’s extendable. We can start the transition process quickly.
10. Current State One year in production. Front-end, back-end and mobile apps using it. The graph of our data is keep growing New app entirely built on top of GraphQL with no work on GraphQL API It’s really extendable, we keep adding new stuff to it without breaking anything.
12. Takeaways
13. GraphQL is extendable, start small
14. Don’t over-use GraphQL types
15. Batching Data Retrievals
16. Caching Micro GraphQL Services ?! Rate-limiting ?! Query Complexity ?!
17. Thanks! Hire me: hi@mv.id.au Follow me: @mattvalleycodes Endorse me: linkedin.com/in/matthew-valley