Open AlexDBlack opened 4 years ago
Kind of related is the ability to do request rate limiting (for clients) and IP filtering. That might be worth looking at also.
This would likely be kubernetes based. We probably shouldn't implement this till we understand what kind of devices we'll be running on. We don't want to write anything more than we have to. Even then, we'll want to look at what vertx already has available.
This isn't an immediate priority, but it's likely that some users will want some sort of authentication for model serving.
For example, suppose a server is publicly accessible to the internet, serving remote IOT devices (or point-of-sale, etc). Clearly we don't want just anyone being able to access such a server and send inference requests, or query the endpoints (such as to get server metrics).