Lessons learned from running GraphQL
blog.dream11engineering.com
Lessons learned from running GraphQL
1–10 of 64 posts
Re: Lessons learned from running GraphQL
#2Since it wasn’t mentioned, I’m curious if they have ever investigated the performance of GraphQL server implementations in other programming languages.
Re: Lessons learned from running GraphQL
#3I wonder if they feel like GraphQL was worth it, vs. normal API servers. Maybe they saved some dev time on the front end, but did that outweigh the dev time spent on building, optimizing, etc? Somehow I doubt it.
Re: Lessons learned from running GraphQL
#4I wonder if they feel like GraphQL was worth it, vs. normal API servers. Maybe they saved some dev time on the front end, but did that outweigh the dev time spent on building, optimizing, etc? Somehow I doubt it.
I wonder if they feel like Node was worth it. (seriously)
Re: Lessons learned from running GraphQL
#5I wonder if they feel like GraphQL was worth it, vs. normal API servers. Maybe they saved some dev time on the front end, but did that outweigh the dev time spent on building, optimizing, etc? Somehow I doubt it.
> Somehow I doubt it
I don't know. They seem to be satisfied customers, and were simply optimizing an already working pipeline in anticipation of saving money.
As a side note, I haven't seen a single "We tried GraphQL and it failed us" story on HN. Not that they don't exist, of course. It's just that there doesn't seem to be much debate about its promise.
Re: Lessons learned from running GraphQL
#6I was considering a similar architecture for something else. It’s nice to see that it basically works to a point because I was worried of exactly the costs they ran into.
Re: Lessons learned from running GraphQL
#7Do I read this right? 1,000,000 requests/sec across 7,500 instances is only 133 requests/second, and graphql wouldn’t typically represent the business logic or data layer.
I love me some graphql, but that seems to be a very low figure. I’m curious how complex the queries are and what else these servers are doing.
Re: Lessons learned from running GraphQL
#8I wonder if they feel like GraphQL was worth it, vs. normal API servers. Maybe they saved some dev time on the front end, but did that outweigh the dev time spent on building, optimizing, etc? Somehow I doubt it.
I’ve been using graphql for years. In my experience, it dramatically simplifies microservice API architecture vs “normal” API servers.
Graphql is super easy to understand, easy to deploy, easy to scale and easy to grow.
It’s not perfect - the lack of namespaces can be a pain, a few more standard types would be good, and mutations feel a bit under baked - but there’s much to love, and very little to dislike.
Re: Lessons learned from running GraphQL
#9>"We provision approximately 7,500 instances for 1 million requests per second."
Looking at this numbers makes me think that a single instance of properly written server running on a single dedicated piece of hardware can handle this without breaking a sweat. My servers for example handle thousands of requests per second. It looks to me like one giant waste of human and hardware resources. Not very "green" approach I would say.
Re: Lessons learned from running GraphQL
#10I wonder if they feel like GraphQL was worth it, vs. normal API servers. Maybe they saved some dev time on the front end, but did that outweigh the dev time spent on building, optimizing, etc? Somehow I doubt it.
> Somehow I doubt it I don't know. They seem to be satisfied customers, and were simply optimizing an already working pipeline in anticipation of saving money. As a side note, I haven't seen a single "We tried GraphQL and it failed us" story on HN. Not that they don't exist, of course. It's just that there doesn't seem to be much debate about its promise.
>"As a side note, I haven't seen a single "We tried GraphQL and it failed us" story on HN"
Why would it "fail". It is just one of many possible protocols to query data. It is like arguing about using this computer language vs that computer language. Bar difference in performance they would all work.