Is GraphQL the Next Frontier for Web APIs? • Hacker News Board

Re: Is GraphQL the Next Frontier for Web APIs?

#71

Post by gary__ » Sat, Apr 01, 2017, 1:38 AM UTC

daxfohl wrote: post #46

misterbowfinger wrote: post #19

Earlier quoted context omitted.

REST is horrible. It encourages new developers to think in terms of CRUD, which is also horrible. It encourages developers to think in terms of data , which is amazing. At the end of the day, we're just doing data transformations, that's it. GraphQL is an interesting iteration on that idea, because it focuses more on the data. REST is simply a way to design your APIs so that they're extensible, usable, and maintainab…

> At the end of the day, we're just doing data transformations, that's it That's kind of the thing though. REST doesn't do transformations. It just does CRUD of resources. For me, when designing an application, I will think, "is representational state transfer the only thing this application will ever need to do?" If the answer is "no" then REST seems like a poor model to build around. I've never answered "yes" to th…

Have you got a link to Fowlers new thoughts on Rich vs Anemic Domain Models?

Re: Is GraphQL the Next Frontier for Web APIs?

#72

Post by [deleted] » Sat, Apr 01, 2017, 1:38 AM UTC

daxfohl wrote: post #46

misterbowfinger wrote: post #19

Earlier quoted context omitted.

REST is horrible. It encourages new developers to think in terms of CRUD, which is also horrible. It encourages developers to think in terms of data , which is amazing. At the end of the day, we're just doing data transformations, that's it. GraphQL is an interesting iteration on that idea, because it focuses more on the data. REST is simply a way to design your APIs so that they're extensible, usable, and maintainab…

> At the end of the day, we're just doing data transformations, that's it That's kind of the thing though. REST doesn't do transformations. It just does CRUD of resources. For me, when designing an application, I will think, "is representational state transfer the only thing this application will ever need to do?" If the answer is "no" then REST seems like a poor model to build around. I've never answered "yes" to th…

[deleted]

Re: Is GraphQL the Next Frontier for Web APIs?

#73

Post by tantan » Sun, Apr 02, 2017, 8:27 AM UTC

I Kaltura.com we auto generate all client libraries in all different coding languages based on auto-generated API descriptor XML that generated using reflection from the server code. It solves most compilation, maintenance and usability issues for integrators. See our clients generator: https://github.com/kaltura/clients-generator See few more server side examples: https://restafar.com/

Re: Is GraphQL the Next Frontier for Web APIs?

#74

Post by tantan » Sun, Apr 02, 2017, 8:27 AM UTC

I Kaltura.com we auto generate all client libraries in all different coding languages based on auto-generated API descriptor XML that generated using reflection from the server code. It solves most compilation, maintenance and usability issues for integrators. See our clients generator: https://github.com/kaltura/clients-generator See few more server side examples: https://restafar.com/