Expert Talk: gRPC, Kubernetes & .NET • Mark Rendle & Matt Turner

Explore the intersection of gRPC, Kubernetes, and.NET as experts Mark Rendle and Matt Turner share insights on API design, container orchestration, and language choices for modern software development.

Key takeaways
  • Terraform is not the best solution for infrastructure as code, as it’s only run once and can lead to drift.
  • gRPC is a great solution for APIs, with its binary protocol and streaming capabilities.
  • .NET 7 will implement gRPC JSON, which is a new feature.
  • Kubernetes is now a standard for container orchestration, but it’s not without its challenges.
  • Language choices, such as Rust and Go, can be good alternatives to Java.
  • Kubernetes is similar to plan 9, in that it provides a standard for containers and orchestration.
  • gRPC can be used for service meshes, and the better libraries emit spans for coding.
  • .NET is a good language, but it has some limitations, such as its image problem.
  • Windows has been around for a long time, and requires careful consideration of its updates and reboots.
  • OpenTelemetry is a complex tool that requires careful application.
  • Kubernetes has many uses, such as streaming and bidirectional streaming.
  • The idea of using a service mesh with gRPC is a good one.
  • Kotlin is a good language that’s similar to .NET.
  • Kubernetes has many features, such as active and passive health checking.
  • The community around Kubernetes is large and active.
  • M$ has made some strange decisions, such as its .NET Core.
  • Cloudflare is a good alternative to traditional databases.
  • gRPC is a good choice for APIs, due to its speed and binary protocol.
  • Java is not the best choice for development, due to its image problem.
  • Go is a good language that’s similar to C.
  • The concept of streaming is important for modern APIs.