3 ms·

Why do you find OData horrible to work with? I've used it with in a personal project and found it to be a very easy way to make my API queryable.

adolph 7y ago
In many relational db implementations OData is a serialization of SQL in a URL. A human factor problem with that is poorly optimized SQL. An architectural problem is that db schema changes break URLs.
- zxienin 7y ago
  To add on this. When you are working with HTTP APIs, do you really need to go full SQL like?
  - adolph 7y ago
    Well, there is a balance. In many circumstances, the same service used by different applications may over-fetch or under-fetch data [0]. OData allows the application to describe exactly what they need including things like filtering, ordering and aggregation that might be less efficient to perform on the application side [1]. Having performed the OData.org Basic Tutorial [2] using just curl, I was positively impressed by the concept and simplicity. 0. https://towardsdatascience.com/graphql-grafana-and-dash-7aa96d940f1b https://towardsdatascience.com/graphql-grafana-and-dash-7aa9... 1. https://www.progress.com/blogs/rest-api-industry-debate-odata-vs-graphql-vs-ords https://www.progress.com/blogs/rest-api-industry-debate-odat... 2. https://www.odata.org/getting-started/basic-tutorial/ https://www.odata.org/getting-started/basic-tutorial/
    - zxienin 7y ago
      > OData allows the application to describe exactly what they need including things like filtering .. I hear this frequently. I have _never_ faced the need to have complex set of capabilities (OData) promising to solve a problem that I do not have. I simply craft my APIs very well. Did you find twilio, stripe, fb.. use OData out in the open? When you offer the real choice to API developer, API consumer and they naturally gravitate to OData, then we're talking. You think developers within SAP ecosystem get choice? Its shoved down their throat. And this is why I believe SAP Graph team is not really serious about "zero SAP knowledge required" crowd.

adolph 7y ago

In many relational db implementations OData is a serialization of SQL in a URL. A human factor problem with that is poorly optimized SQL. An architectural problem is that db schema changes break URLs.

zxienin 7y ago
To add on this. When you are working with HTTP APIs, do you really need to go full SQL like?
- adolph 7y ago
  Well, there is a balance. In many circumstances, the same service used by different applications may over-fetch or under-fetch data [0]. OData allows the application to describe exactly what they need including things like filtering, ordering and aggregation that might be less efficient to perform on the application side [1]. Having performed the OData.org Basic Tutorial [2] using just curl, I was positively impressed by the concept and simplicity. 0. https://towardsdatascience.com/graphql-grafana-and-dash-7aa96d940f1b https://towardsdatascience.com/graphql-grafana-and-dash-7aa9... 1. https://www.progress.com/blogs/rest-api-industry-debate-odata-vs-graphql-vs-ords https://www.progress.com/blogs/rest-api-industry-debate-odat... 2. https://www.odata.org/getting-started/basic-tutorial/ https://www.odata.org/getting-started/basic-tutorial/
  - zxienin 7y ago
    > OData allows the application to describe exactly what they need including things like filtering .. I hear this frequently. I have _never_ faced the need to have complex set of capabilities (OData) promising to solve a problem that I do not have. I simply craft my APIs very well. Did you find twilio, stripe, fb.. use OData out in the open? When you offer the real choice to API developer, API consumer and they naturally gravitate to OData, then we're talking. You think developers within SAP ecosystem get choice? Its shoved down their throat. And this is why I believe SAP Graph team is not really serious about "zero SAP knowledge required" crowd.