Recent searches
Search options
I've been immersed in GraphQL recently. You know, it's pretty great, actually. Are there issues? Yeah. It's impossible to design a system like this perfectly. Yeah, maybe it was made by "Facebook", but in reality it was made by engineers who worked at Facebook and is controlled by a neutral non-profit. It's does a few things *extremely* better than REST: change/versioning, pulling multiple related or unrelated bits of data in a single request, and only sending the fields you need.
1/n
@thezerobit interesting, thanks. I recently began building my first REST API so learning, learning, learning and have GraphQL on my list to look into.
No reason I can't offer both at least in the short term so your comments are welcome.
One issue I guess is the level of support, esp for a novice.
I found a actix + utoipa have helped a lot as I'm coding on a Rust backend. Do you know if there are similar tools to help with #GraphQL+ #Rustlang?
@happyborg
If you're building your first REST API, I would suggest avoiding GraphQL for now. GraphQL is quite a bit more complicated and while it is technically built on top of REST/HTTP, it doesn't really follow the design philosophy of REST and tunnels it's own model of representing state and change via a single POST endpoint.
Rust isn't in my wheelhouse, so I don't know what the good GraphQL libraries are, if there are any.