Hacker News Reader

I'm using it at work to develop an API and I'd say that it's been a great experience. I find that it fits well with our use case.

I find it works well for when we need to collect information from several places at once which in our older API required several requests to REST endpoints. Now we have a single request and a much faster response time.

View on HN

> I find that it fits well with our use case.

What's your use case? Also, how difficult is it to create and maintain the API? I hear nothing but good things about it from the frontend people, but some of the backend people I've asked about it just mutter to themselves about increased complexity then run away. Which also makes me think I need to become friends with backend people who don't mutter to themselves, but one thing at a time.

A platform which handles listings and bookings. I work primarily on the backend and haven't really felt any discomfort in terms of complexity. It just gives a lot of flexibility in how we work with the data that we have and what we can offer to the frontend.

The stack is GraphQL Yoga and Prisma which simplifies things quite a bit!

Reply on news.ycombinator.com