rest - GraphQL not for public API -


is graphql overkill regular application, not public api? if develop application know endpoint need return predefined set of data.

what benefits can give graphql comparing rest or rpc, if develop both, backend , frontend.

whether it's overkill more matter of scale , effort else. directly address first question, graphql designed "regular applications" rather public apis - use latter relatively new thing being pioneered community rather graphql's creators.

rather repeating answers exist in numerous forms in numerous places, i'm going suggest watch of original talks introducing graphql world, these got adopters excited, , should answer lot of questions:

data fetching react applications @ facebook

lee byron - exploring graphql


Comments

Popular posts from this blog

networking - Vagrant-provisioned VirtualBox VM is not reachable from Ubuntu host -

c# - ASP.NET Core - There is already an object named 'AspNetRoles' in the database -

ruby on rails - ArgumentError: Missing host to link to! Please provide the :host parameter, set default_url_options[:host], or set :only_path to true -