Using Convex to expose an HTTP API
hey, so we are going to go 100% convex for a new service.
We do not need a client exposed api yet, but we will in the future. one of the ideas we'd like to see is autogenerated docs "openapi" and validation for api endpoints if we use convex to host our rest api.
if hosting the rest api, we would like the ability to add things like rate limits, etc. to prevent bad actors.
if this is not the intended direction/use case of convex longterm, would like to understand the best way to consume the convex database from our external rest api - e.g., created in Go.
@jamwt @james
We do not need a client exposed api yet, but we will in the future. one of the ideas we'd like to see is autogenerated docs "openapi" and validation for api endpoints if we use convex to host our rest api.
if hosting the rest api, we would like the ability to add things like rate limits, etc. to prevent bad actors.
if this is not the intended direction/use case of convex longterm, would like to understand the best way to consume the convex database from our external rest api - e.g., created in Go.
@jamwt @james
