Though seriously there’s nothing wrong with having a single endpoint that accepts commands rather than trying to be whatever “REST” means this week. Just not raw SQL please.
Yeah most developers haven’t the slightest clue what it means. Most people use it to mean a shitty version of a RPC API with a bad query language.
If you’re going to do that, you may as well use something that’s actually meant for that, like the numerous RPC protocols available. Or hell, even GraphQL (which is basically what you’re saying).
REST can take different forms, but all of them necessarily require you to be talking hypermedia-enabled APIs. If your resources (read: not endpoints, which are not a concept in REST) do not contain links to other resources, you aren’t doing REST and you should stop pretending that you are.
Though seriously there’s nothing wrong with having a single endpoint that accepts commands rather than trying to be whatever “REST” means this week. Just not raw SQL please.
Yeah most developers haven’t the slightest clue what it means. Most people use it to mean a shitty version of a RPC API with a bad query language.
If you’re going to do that, you may as well use something that’s actually meant for that, like the numerous RPC protocols available. Or hell, even GraphQL (which is basically what you’re saying).
REST can take different forms, but all of them necessarily require you to be talking hypermedia-enabled APIs. If your resources (read: not endpoints, which are not a concept in REST) do not contain links to other resources, you aren’t doing REST and you should stop pretending that you are.
That’s what everyone calls GraphQL now lol