3 ms·

I would love to see a full comparison of an API like the one mentioned in the article and full-fledged REST API (built with cacheability in mind) having somethi

• obcilion 5y ago
  It is a full-fledged REST API, but we don't do a lot of caching (other than through Cloudlfare) as most of our endpoints either have volatile data or do various operations.
  • nesarkvechnep 5y ago
    Is it hypertext-driven? When I say REST API I don’t mean just an HTTP-based interface.
    • obcilion 5y ago
      It's REST but we don't do HATEOAS. All indicators points to it being a lot of work with little to no reward.
      • dragonwriter 5y ago
        > It's REST but we don't do HATEOAS. So, it's nothing at all like REST. > All indicators points to it being a lot of work with little to no reward That depends what you are doing, but, yes, REST is the wrong solution for lots of problems, but that's not a good reason for calling whatever the non-REST thing is that you’ve chosen to do instead “REST”. REST is at it's core hypertext as the engine of application state, it is an architectural pattern developed for and as part of the process of refining standards for the WWW; everything else about it is details of how you do HATEOAS. If you aren't doing HATEOAS, you aren't, even approximately, doing REST.