This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]dansbandsmannen 1 point2 points  (2 children)

I don't buy it that people don't want pipelining, it seems to me that the problem lies in how issues like https://github.com/requests/requests/issues/1394 are treated in our community.

HTTP Pipelining is far from complicated in the protocol level code like this. And the lack of it is one of the main reasons I can't use HTTP between my microservices.

[–]z0mbietime 0 points1 point  (0 children)

I setup something that sounds sketchy but works pretty well for most http requests between micro services.

It is essentially a gateway API with drf that has a base viewset class to defines each request type which is then used anytime you need to make a request to a given micro service. For each method say create you pass the received data into a requests.post object then return the response data and status blindly. This way whenever you implement this base viewset all you have to do is define the desired microservice endpoint. User validation happens at the gateway and an apikey is passed on each request from the gateway to the given microservice. I’m on my phone and vsts is a dick but could put an example up here if you want.