From @askcarter: "Consider adding a bit about 'best practices' for implementing our APIs this way. IE, mocking out responses, so that we always have something to test / work with. This works well for TDD or prototype driven development." as a response to #13

Cc: @abhisekpan

"Just a suggestion!
in this slide / page,
https://github.com/vjpai/grpc-tutorial/blob/master/slides/parallel-models.md,
in platforms - maybe add peer-to-peer systems, and also grid-computing
systems."

Many users are interested in FlatBuffers. gRPC only officially supports protos or raw bytes, but there have been community bindings for FlatBuffers. Consider using this in some course examples.

• Go

  • Pro: great learning tool, easy to install, seamless integration with other Google-based learning experiences (such as kubernetes class), easy to express concurrency
  • Con: Heavily used but not necessarily widely; many users are already experienced with principles of building microservices. No idiomatic way to express async RPCs.

• Python

  • Pro: Seamless gRPC installation process, possibly the most widely used language in general
  • Con: Like other GIL-based languages, may be overly slow

• Other choices?