Agreed that once I am on a team that needs something different, I’ll adhere to the norms of that team.
Side projects, if you can make the time in your life, are a great place to experiment with this stuff because it is just me. Also, most of my side projects are disposable so I don’t have to worry about long term maintenance. :-)
Great work! I love the way that you explore multiple solutions and judge them based on readability and ease of adding new features.
This experiment is a great illustration about what happens when we add levels of abstraction too early in a codebase. We run the risk of new feature requests not fitting into the abstractions…
Most of the articles I’ve seen on GraphQL focus on the query side of the interaction…and I agree that GraphQL beats REST there because I can specify what data I get read.
Do you have any example of using a GraphQL API to write? I took a look at the spec and it seems a little light on the details. Maybe I’m missing something.