Improving API Response Times by Migrating from Cloud Functions to Cloud Run

Re:Improving API Response Times by Migrating from Cloud Func... by nesarkvechnep on Tuesday January 11, 2022 @11:47AM (#29893925)

Is it hypertext-driven? When I say REST API I don’t mean just an HTTP-based interface.

[ Parent | on HN ]

Re:Improving API Response Times by Migrating from Cloud Func... by obcilion on Wednesday January 12, 2022 @03:05AM (#29903672)

It's REST but we don't do HATEOAS. All indicators points to it being a lot of work with little to no reward.

[ Parent | on HN ]

Re:Improving API Response Times by Migrating from Cloud Func... by dragonwriter on Wednesday January 12, 2022 @03:15AM (#29903735)

> 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.

[ Parent | on HN ]