The permitting backend already speaks gRPC, while the public web form already calls the same live model over REST. What should the service-side caller do?
Select an answer to reveal the explanation.
Short Explanation
The public form already speaks REST. The permitting backend already speaks gRPC. Keep one Triton or NIM copy and add a gRPC client on the service. Protocol is a client choice, not a second model, a broken browser, or a cuDF job.
Full Explanation
REST and gRPC are client protocols in front of the same served model. A backend that already speaks gRPC should add a gRPC client and keep one Triton or NIM copy. Duplicating the model per protocol wastes capacity. A browser form should stay on REST, and a RAPIDS wrangle is not a serving protocol.