News for hackers. Stuff that matters.
Re:Goodbye Microservices: From 100s of problem children to 1... by bsder on Tuesday July 10, 2018 @06:44PM (#17502856)
Repeat after me: there is no such thing as a synchronous network.

I get where you are coming from. But you will go async sooner or later if you need any reasonable error recovery or reliability.

The only question is how much pain you will suffer before you do so.

Re:Goodbye Microservices: From 100s of problem children to 1... by thermodynthrway on Tuesday July 10, 2018 @07:24PM (#17503088)
This is just not true. Google uses almost entirely immediately consistent databases and gRPC internally. Eventual consistency is hardly ever required for REST type calls even at massive scale.

gRPC has no queuing and the connection is held open until the call returns. All of Google's cloud databases are immediately consistent for most operations

Re:Goodbye Microservices: From 100s of problem children to 1... by jacques_chester on Tuesday July 10, 2018 @07:53PM (#17503268)
My understanding is that Spanner is optimistically immediately consistent, with very clever logic for deciding on whether to bounce the attempted transaction (TrueTime).

But strictly speaking, even inside a single multicore CPU, there is no such thing as immediate consistency. The universe doesn't allow you to update information in two places simultaneously. You can only propagate at the speed of light.

Oh, and the concept of "simultaneous" is suspect too.

Our hardware cousins have striven mightily and mostly successfully for decades to create the illusion that code runs in a Newtonian universe. But it is very much a relativistic one.