i still haven't picked up graphql, might spend sometime next weekend seeing what it has to offer. anyone have any advice or stories?

I used the basic syntax for a project which didn’t had time for proper JSON api’s.

That’s it, can’t be bothered to learn more. Why should I? Done right, it’s most of the time a bit too overkill and I like my good ol swagger specs.

As with many things, it’s a small performance sacrifice for convenience.

It’s nice.
But it isn’t difficult to write an API for specifically what you need.

It’s pretty nice but doesn’t cover all the needs, you can use hasura and you don’t need to write any code for your graphql backend.

If you are on dotnet: Don't think graphql.net is somehow more native or official. It's usable, but take a look at their github issues. I've had much more luck with hot chocolate.

Graphql is not a better or worse compared to rest. It just solves different issues. It was essential for our project due to a massive and massively complex domain model which pulls data from half a dozen different sources, has circular relationships, and needs to paginate on these deep nested relationships; eg. phone number for the 835th employee sorted by date registered on company X filtered by being an owner of Y.

The frontend guys have commented they can never go back to rest after using it. Us in backend need a lot of convincing before using it in a new project.

Graphql as front end or backend here?

this will change your life! It's amazing to deliver data to your clients, my advice is to use it as bff rather than a BE service. I have found it very useful to use lambda as your micro service stack and just deliver data and mutate from GQL to your clients connected through Apollo.

Apollo can’t into websockets everything else good k bye

It's cool, until you see the abomination of a webservice Shopify calls API 🧐