Stop using REST

Attached: 1640095458945.png (658x204, 33.53K)

I don't use fully restful API only get and post methods. It's enough, http verbs are not just semantic.

>everything is about performance

Next scrum topic: how can we make our APP more Perfornant?

No. I only care about performance if it effects user experience or if someone complains. I can shit out REST APIs very quickly without having to learn or do anything new.

Ok but when the team from Poland accesses the API can you send back their numbers as strings? We need to accommodate their legacy software. The Indians also need some simpler documentation. Clock's ticking pal, I'm putting this on you for the end of the week.

Good fucking luck load balancing your gRPC api.

What did he mean by this?

Can't tell if you're a pajeet or just autistic. Either way you're stupid.

Scale out is cheap. Extra dev time for muh buffers less so

>grpc
Anything that uses http as a transport layer can safely be discarded.

By not hiring pajeets

What should we use instead? WebSockets?

He means you won't be able to reuse existing HTTP load balancing solutions.

Attached: 1662815426662271.png (512x512, 419.38K)

> grpc
> google
> remote
> procedure call

Embrace, extend, extinguish.
Reject the call of the Google siren, embrace non-google open web standards

this
And they breeze through corporate firewalls.

>Ok but when the team from Poland accesses the API can you send back their numbers as strings?
Done
>The Indians also need some simpler documentation.
Indians don't read documentation. Just touch the file so the timestamp changes and send it again.

You can use haproxy you niggerjeet

>not flexible in terms of the way its sent so if you have to refractor from JSON to pseudo typed
how about no.

Why in the ever living fuck would I be doing 30MB/s of RPCs?

And with HTTP2?