Hi Heithem, I wouldn't call REST off. Most APIs are still REST based.
What I see now are three main approaches in API development:
REST (or RESTish, because most public APIs I work with don't have the hypermedia part of REST)
GraphQL
gRPC
I've never tried gRPC so I can't provide an opinion but I hear is very efficient. AFAIK it requires HTTP/2 by default, so this might slow down its adoption on public APIs. I would definitely consider it if I controlled both ends of the application though (and when not using Heroku).
I think, for now, GraphQL has made more a splash in term of adoption than gRPC.
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.
Hi Heithem, I wouldn't call REST off. Most APIs are still REST based.
What I see now are three main approaches in API development:
I've never tried gRPC so I can't provide an opinion but I hear is very efficient. AFAIK it requires HTTP/2 by default, so this might slow down its adoption on public APIs. I would definitely consider it if I controlled both ends of the application though (and when not using Heroku).
I think, for now, GraphQL has made more a splash in term of adoption than gRPC.