DEV Community

Discussion on: Why I no longer use GraphQL for new projects

Collapse
 
jyoost profile image
jyoost

If the project has a disconnected front end from the get go then I would definitely use graphql from the start.

A rest API is a bad fit for js framework frontends. In fact js frameworks are a bad fit for web projects in general, but that is a whole other discussion. 😂

If your web app is rendered server side, there is no need for an API or GRAPHQL at the start.

Using django + htmx + alpinejs you can create a pwa that competes with the best.

Later you can add DRF , graphene. graphene will generate graphql from DRF or django forms.

A good example of a project that was great until it was rewritten as a disconnected js framework (react) with graphql. Is saleor by miramee.

2 years after they started the conversion it is still a pile.

If they spent the resources on improving the django app (that already worked) it would be a great product without bouncing balls or cutesy thing to cover up how slow it is.

Why is it that server-side apps don't need cutesy gadgets to amuse you while you wait?