News for hackers. Stuff that matters.
Re:Istio Observability with Go, gRPC, and Protocol Buffers-B... by sklivvz1971 on Sunday April 21, 2019 @04:18PM (#19714314)
I found this interesting and an excellent general overview of today's monitoring practices while using microservices.

I have to say, though, that I am always perplexed by these toy microservice architectures because they are not solving a problem but creating it. For example, we would not need sophisticated distributed tracing if we used less moving parts; we would not need to use highly optimized (but hard to debug) protocols like grpc and protobuf if we did not have to rely on a massive graph of calls for each service, and so on.

Of course, there are a bunch of lovely use cases for microservices, mostly around "how do we make 1k developers collaborate over our codebase?" (answer: enlarge the codebase!), which always sounded like a self-fulfilling prophecy to me, but then again, I loathe working for huge companies.

If that is your case, then these tools will make your developer life a little more bearable. If you are playing with microservices because they are fresh and new, please consider a more conservative architecture first.

Re:Istio Observability with Go, gRPC, and Protocol Buffers-B... by orf on Sunday April 21, 2019 @05:15PM (#19714630)
These solutions didn’t appear out of thin air because people get bored one day. Micro services solve tangible, real world problems.

gRPC isn’t necessary hard to debug, and it brings a whole host of improvements over whatever ad-hoc mess you used before.

Re:Istio Observability with Go, gRPC, and Protocol Buffers-B... by ioquatix on Sunday April 21, 2019 @05:27PM (#19714680)
Improvements like...?
Re:Istio Observability with Go, gRPC, and Protocol Buffers-B... by orf on Sunday April 21, 2019 @05:50PM (#19714781)
Speed, schemas, code generation, built in backwards compatibility, extension points, public service definitions, introspection to name a few.
Re:Istio Observability with Go, gRPC, and Protocol Buffers-B... by Thaxll on Sunday April 21, 2019 @09:03PM (#19715605)
You forgot real bi-directional streaming but otherwise I agree :)
Re:Istio Observability with Go, gRPC, and Protocol Buffers-B... by mping on Sunday April 21, 2019 @05:44PM (#19714749)
Performance, I guess. Also, a schema. Eg json has schema but most apis I know don't use json schemas.
Re:Istio Observability with Go, gRPC, and Protocol Buffers-B... by sklivvz1971 on Sunday April 21, 2019 @05:43PM (#19714744)
> These solutions didn’t appear out of thin air because people get bored one day.

I certainly did not say these architectures appeared out of thin air. They were invented to solve the problems of internet-scale companies.

> Micro services solve tangible, real world problems.

Incorrect. Microservices solve tangible, real-world problems when they are applied to the correct problems. Microservices might also create tangible, real-world problems whether they are applied correctly or not. In fact, that's one of the points of the article, if you read between the lines.

> gRPC isn’t necessary hard to debug, and it brings a whole host of improvements over whatever ad-hoc mess you used before.

I don't know what you are referring to. If your microservices are well done, good for you. You still need to optimize the transport, which is a cost you pay only because of your choice of architecture. If you used thicker services or a monolith you would have different problems, but not that one.