Worked with GraphQL from 2017 to 2021. It was the last tech "hype" I bought into. At first, it made a lot of sense and the thing that got me was the structure.

Worked with GraphQL from 2017 to 2021. It was the last tech "hype" I bought into. At first, it made a lot of sense and the thing that got me was the structure. But eventually, I realized how much extra work and duplication of everything there was. At the time, too, things that should have been easy like subscriptions had a nightmare API packed with weird terminology that made implementing simple features a slog. The one positive to come out of working with it (aside from knowing how to spot a tech black hole) is that it informed the design of the API layer in my framework [1][2]. I realized the sweet spot is starting with a basic JSON-RPC type endpoint and then layering things like input validation [3], authorization [4], and selective output [5] (only requesting certain fields back) on as you need them. [1] https://docs.cheatcode.co/joystick/node/app/api/getters https://docs.cheatcode.co/joystick/node/app/api/getters [2] https://docs.cheatcode.co/joystick/node/app/api/setters https://docs.cheatcode.co/joystick/node/app/api/setters [3] https://docs.cheatcode.co/joystick/node/app/api/validating-input https://docs.cheatcode.co/joystick/node/app/api/validating-i... [4] https://docs.cheatcode.co/joystick/node/app/api/authorization https://docs.cheatcode.co/joystick/node/app/api/authorizatio... [5] https://docs.cheatcode.co/joystick/ui/api/get https://docs.cheatcode.co/joystick/ui/api/get (see output array in the function options API)