why is it not considered an architectural pattern? RESTful APIs depend on URIs specific to resources whereas GraphQL can in simple cases remove that.
"The acronym REST stands for Representational State Transfer, this basically means that each unique URL is a representation of some object"
Without a URL for each object, we don't have a RESTful API pattern. Is it then not fair to say that GraphQL can replace RESTful API architecture?
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.
why is it not considered an architectural pattern?
RESTful APIs depend on URIs specific to resources whereas GraphQL can in simple cases remove that.
"The acronym REST stands for Representational State Transfer, this basically means that each unique URL is a representation of some object"
Without a URL for each object, we don't have a RESTful API pattern. Is it then not fair to say that GraphQL can replace RESTful API architecture?