gRPC for Microservices Communication

Post by [deleted] » Thu, Sep 23, 2021, 9:29 PM UTC

Zababa wrote: post #20

mirekrusin wrote: post #12

"In the olden days, a software application was built as a large monolith (...)" - people should stop writing this kind of shit. You can hear this nonsense from some poor quality bloggers. People who are serious about it say things like "for most startups microservices is bad idea", "monolith should be starting point in most cases", "there is a price that comes with microservices", "modularised monoliths are often pef…

I especially dislike when people talk about microservices and scalability like they are a solution. Most companies won't see the kind of scale Facebook/Google/etc sees, not because they won't have that much clients, but also because there's a good chance that they don't need all clients in the same system. Most business don't benefit from the network effect. In that case, your scale is not the total sum of the size o…

Post by Smaug123 » Thu, Sep 23, 2021, 9:40 PM UTC

sfblah wrote: post #24

georgeburdell wrote: post #23

Related question: is gRPC the anointed successor to WCF for .NET? I'm looking at a re-write of our mostly monolithic code at work, which uses C# on an old framework with a little WCF to communicate with one service, and got a bit concerned as WCF appears to be on the way out in the new .NET Core versions.

I think it basically is. I've done work for a company using .Net Core since about 2018. Back then, you had to use the Google stubs and work around a lot of the Microsoft host setup to get it to work. These days, gRPC seems to be on par with REST as a framework. That said, I'd like to see better support for C# code generation from proto files. For example, the support for nullable types works ok but is a bit cumbersom…

Post by cbsmith » Thu, Sep 23, 2021, 9:41 PM UTC

gokhan wrote: post #30

I love the cyclical nature of everything in remote execution world. Corba, Remoting, some XML sauce, WCF, Http methods and Url's, some Json sauce, and than gRPC. Same ideas. Just like having flared trousers every 10 years or so. Payload is binary, it's fast -> Anybody can read the payload but it's structured -> Structure is redundant, look how lightweight is this -> Payload is binary, it's fast The problem in softwar…

Post by brown9-2 » Thu, Sep 23, 2021, 9:59 PM UTC

baldeagle wrote: post #3

Is this the path to a tightly coupled distributed monolith?

Post by jayd16 » Thu, Sep 23, 2021, 10:02 PM UTC

Zababa wrote: post #20

mirekrusin wrote: post #12

"In the olden days, a software application was built as a large monolith (...)" - people should stop writing this kind of shit. You can hear this nonsense from some poor quality bloggers. People who are serious about it say things like "for most startups microservices is bad idea", "monolith should be starting point in most cases", "there is a price that comes with microservices", "modularised monoliths are often pef…

I especially dislike when people talk about microservices and scalability like they are a solution. Most companies won't see the kind of scale Facebook/Google/etc sees, not because they won't have that much clients, but also because there's a good chance that they don't need all clients in the same system. Most business don't benefit from the network effect. In that case, your scale is not the total sum of the size o…