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
saved by
related reading
- Everything I know about good API designseangoedecke.com
- Building data-centric apps with a reactive relational databaseriffle.systems
- Against SQLscattered-thoughts.net
- The Elements of UI Engineering — overreactedoverreacted.io
- Why We Don’t Trust the Database With Authentication – Sturdy Statisticsblog.sturdystatistics.com
- Software development topics I've changed my mind on after 10 years in the industrychriskiehl.com
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- The new wave of Javascript web frameworksfrontendmastery.com
- Second-guessing the modern web - macwright.commacwright.com
- The Problem with OpenTelemetrycra.mr
- A Graph-Based Firebasestopa.io
- You might not need Redisviblo.se