psturgeon

6 ms·

1.
by psturgeon 5y ago
I covered all of that in a previous article and many more since. https://apisyouwonthate.com/blog/graphql-vs-rest-caching Basically, trimming a few bits off of a request is not overall quicker than helping clients not
2.
by psturgeon 5y ago
Did you read the link you shared? 19.7.1 Compatibility with HTTP/1.0 Persistent Connections Some clients and servers may wish to be compatible with some previous implementations of persistent connections in HTTP/1.0 client
3.
by psturgeon 5y ago
The whole "REST is good and everything else is dumb" is something I've tried to help people get away from for about a decade. These days it's GraphQL is good and everything else is dumb. See some of the comments in here.
4.
by psturgeon 5y ago
If you make your quotes small enough you can make them mean anything, but I invite you to go take a look at the dissertation. "large-grained resources" does not mean "compound documents", the REST dissertation has no com
5.
by psturgeon 5y ago
That's a constructive comment based on a well rounded understanding of the various architectures and paradigms around. You sound well balanced and like you're a pleasure to work with.
6.
by psturgeon 5y ago
GraphQL, OData, and JSON:API some of many compound document implementations you can use to mush multiple resources into a single request, this article was about how doing that is pointless and sometimes detrimental.
7.
by psturgeon 5y ago
Ignoring all the layers of HTTP to use it as a dumb tunnel is a really effective way of forcing everyone to reinvent a lot of wheels at every phase of the interaction. A lot of people do it, its usually a brittle and expensive waste of time
8.
by psturgeon 5y ago
There's loads of problems and I've been talking about them all through a series of blog posts and talks, I just didn't cover it here. The main problem is that tertiary data slows down primary data. Put simply, when you reques
9.
by psturgeon 5y ago
Which modern company am I writing from? WeWork? Mate that place was a global shitshow. Funny backstory if you're interested. https://phil.tech/2020/prioritizing-api-ecosystem-maturity/ No my article was not i
10.
by psturgeon 5y ago
RPC thinking is one way of doing things, but not making a call is quicker than making a call. Took me a while to figure that one out too. If this article hasn't helped, see if fastly can make some of these points better. https:/&
11.
by psturgeon 5y ago
As a consultant I meet a lot of people who think the goals of REST are pointless and have created an absolute shitshow of poor API design, reinventing loads of wheels and getting to a point they had to get me to come in. Usually explaining
12.
by psturgeon 5y ago
Hi, I am not assuming all microservices are in the same data center. Your reply assumes that API requests need to be made in sequence. If you need 3 resources, and you make 3 requests, you are not waiting for 1 then 2 then 3. 1 and 2 and 3
13.
by psturgeon 5y ago
It sounds nice at first, but if you have 5 completely different resources then why would you want to squish them into one? This taints highly cacheable data with frequently changing data, and slows down everything all at the same time. Also