You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an API user, I'd like to be able to supply a query for precisely the data that I want regardless of how the underlying database is structured. I can live with it being read-only in the short term.
The gain is that I can make 1 API call to get the data I want without having to make N rest calls to stitch together the dataset. It also allows me to not pay the price for data that is irrelevant, but normally returned by the rest interfaces. It also allows me to build complex filters as part of that query so I don't have to parse responses the size of /servers for example. It also gives me pagination of results too.
It would be evaluating how much of our existing golang TO Structs could be reused for this effort already.
The text was updated successfully, but these errors were encountered:
As an API user, I'd like to be able to supply a query for precisely the data that I want regardless of how the underlying database is structured. I can live with it being read-only in the short term.
The gain is that I can make 1 API call to get the data I want without having to make N rest calls to stitch together the dataset. It also allows me to not pay the price for data that is irrelevant, but normally returned by the rest interfaces. It also allows me to build complex filters as part of that query so I don't have to parse responses the size of
/servers
for example. It also gives me pagination of results too.It would be evaluating how much of our existing golang TO Structs could be reused for this effort already.
The text was updated successfully, but these errors were encountered: