bairen

Its silly to think protobufs code gen is a advantage. I can take a json object/xml/csv from any API and plug it into a website that will spit out models in any language I want.

The only real advantage of grpc and protobufs have are speed and reduced data transmission.

And hey fair enough man if those are your bottle necks.

Yes, using envoy was bad design in our situation. It was premature optimisation.

We could either maintain a grpc API and a rest API , or a grpc API plus envoy, or 1 rest API.

I am saying we should have picked 1 rest API and only switched to grpc if and when we ran into scaling problems.

Avoiding having to maintain grpc compilers and envoy in our security updates.

We use a few of the endpoints in the backend. Service to service communication.

Those same endpoints are used with envoy. By our UI.

That choice was made to reduce code bloat.

Rather than maintain grpc and envoy it's easier to just maintain 1 rest API.

The service to service communication was never a bottle neck.

So it was highly prematurely optimized.

We spend way more time keeping evoy and our grpc compilers up to date and free of security issues than I would like.

It's just extra software and thus extra attack surfaces we didn't need. In retrospect

We ended up wrapping them in envoy so that our UI can convert the grpc to regular old http 1. And that's where they get the most use.

And by doing that we've added extra layers and it ended up slower than it would have been had we just used regular rest.

Further more now we need to keep evoy up to date.

Occasionally they break their API on major versions. Their config files are complicated and confusing.

So, imo, grpc should only be used for service to service communication where you don't want to share the code with a UI and speed and throughput is very very important.

And speed of http 1 rarely is the bottleneck.

We built a backend heavily using protobufs/grpc and I highly regret it.

It ads an extra layer of complexity most people don't need.

You need to compile the protobufs and update all services that use them.

It's extra software for security scans.

Regular old http 1 rest calls should be the default.

If you are having scaling problem only then should you consider moving to grpc.

And even then I would first consider other simpler options.

It really is silly it was classified as more dangerous than cocaine.

A drug that you can actually overdose on.

No you don't get to look at these graphs and claim a 90 ldl has the same outcomes as a 140.

That's just lying.

Yes there are edge cases. You could get hit by a car with a 140.

It's looking at all cause mortality.

A higher ldl seems to be protective. Of course it is. The body makes it for a reason.

That's a pretty low carb intake. I do a good bit of cardio and will cramp really bad when I'm under 50g of carbs.

I try to only get carbs from fruit, milk, and potatoes to keep the carbs clean.

Yeah it's crazy. Meat eaters are eating chicken fried in seed oils with soda.

Take away the sugar, alcohol ,and seed oils and meat eaters are all healthy.

It was a study of studies. The studies were meta analysis.

In other words this study used zero direct observational studies.

No one has ever fed one person a meat diet and another person meat free diet and shown there to be a increase or decreased risk of heart disease.

Daily reminder that Hong Kong has one of the highest meat consumption per person in the world And one of the highest life expectancies.

India has some of the lowest meat consumptions in the world and one of the lowest life expectancies.

So clearly meat is not the demon some of these biased studies make it out to be.