A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Memes and software development shitposting
Discussing AI software development, and showing off what we're building.
Movie and TV enthusiasm, criticism and everything in-between.
Web design, graphic design and everything in-between
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
I learnt today that there are actually three things or more...
graphql.org/learn/serving-over-http/
After reading a lot about the differences between REST and SOAP, I got the impression that REST is just another word for HTTP. Can someone explain what functionality REST adds to HTTP?
Note: I'm not looking for a comparison of REST versus SOAP.
Update: Thanks for your answers…
It feels like GraphQL and REST API are actually apples and oranges.
This seems to be a correct answer.
hasura.io/blog/rest-view-of-graphql/
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I learnt today that there are actually three things or more...
graphql.org/learn/serving-over-http/
After reading a lot about the differences between REST and SOAP, I got the impression that REST is just another word for HTTP. Can someone explain what functionality REST adds to HTTP?
Note: I'm not looking for a comparison of REST versus SOAP.
Update: Thanks for your answers…
It feels like GraphQL and REST API are actually apples and oranges.
This seems to be a correct answer.
hasura.io/blog/rest-view-of-graphql/