Two protocols, two use cases
TF Serving exposes both REST (port 8501) and gRPC (port 8500). REST is easiest — standard HTTP JSON requests, integrate from anything. gRPC is faster — binary Protocol Buffers serialization, lower latency, lower bandwidth for high-volume production traffic.
REST URL pattern: http://host:8501/v1/models/{MODEL_NAME}:predict. Add /versions/{N} to target a specific version.
For Python clients, REST is two lines (requests.post). gRPC needs the tensorflow-serving-api package and Protocol Buffer message types.
When to use which: REST for development, debugging, low-volume production, integration with web frameworks. gRPC for high-throughput production where serialization overhead actually shows up in latency budgets.