Why, after 6 years, I’m over GraphQL
GraphQL is an incredible piece of technology that has captured a lot of mindshare since I first started slinging it in production in 2018. You won’t have to ...
GraphQL is an incredible piece of technology that has captured a lot of mindshare since I first started slinging it in production in 2018. You won’t have to look far back on this (rather inactive) blog to see I have previously championed this technology. After building many a React SPA on top of a hodge podge of untyped JSON REST APIs, I found GraphQL a breath of fresh air. I was truly a GraphQL hype train member. However, as the years have gone on and I have had the opportunity to deploy to environments where non functional requirements like security, performance, and maintainability were mor
Explore this link on the map →saved by
related reading
- Against SQLscattered-thoughts.net
- Everything I know about good system designseangoedecke.com
- Everything I know about good API designseangoedecke.com
- A Graph-Based Firebasestopa.io
- Second-guessing the modern web - macwright.commacwright.com
- SQL as APIvalentin.willscher.de
- Resolvers - Apollo GraphQL Docsapollographql.com
- SOOTplay.soot.com
- Roam Research – A note taking tool for networked thought.roamresearch.com
- Best practices for REST API design - Stack Overflowstackoverflow.blog
- Building Graphite: our experience with TypeORMgraphite.dev
- Reading and writing data to the cache - Apollo GraphQL Docsapollographql.com