DEV Community

Discussion on: Rest v/s GraphQL !

Collapse
badpractice profile image
Bad Practice

I don't find GQL to be the perfect end-all for more intense scenarios. People tend to forget how easy it is to combine data similar to graphql in postgresql with simply a WITH clause. Processing transactions, subscriptions, notifications, all in a single query if you wanted to do a wallet based subscription.

From my perspective, I just find graphql to be another sign of convenience, a sense of escapism from the raw values of lowish-level relational data management. REST is so easy if you know how to reduce I/O, minimize your mappings, and figure out to reduce the amount of queries, especially when there's math involved.

I'm not against graphql as I've thought about giving it a shot. But I already have PTSD from Symfony/Doctrine's ORM mappings.

Collapse
ericwooley profile image
Eric Wooley

Checkout hasura. It creates queries by analyzing your graphql request. So it's generally very efficient

Collapse
badpractice profile image
Bad Practice

On YouTube, maybe Twitch, I'm actually going to be doing a series soon showing my own methodologies on building slightly complex sites, but starting off with simpler ones just to give people ideas whether they're new or experienced.

Collapse
negreanucalin profile image
Negreanu Calin

Can't wait for the series, leave sime links :)
Thanks for the service ;)