The article pretty much sums up why I've been a bigger fan of OData than GraphQL, especially in the business cases. OData will still let you get all those same wins that GraphQL does but without a sql-ish query syntax, and sticking to the REST roots that the web works better with. Also helps that lots of Microsoft services work out of the box with OData.

in my experience OData has several big issues:

- Overly verbose endpoint & request syntax: $expand, parenthesis and quotes in paths, actions etc.

- Exposes too much filtering control by default, allowing the consumer to do "bad things" on unindexed fields without steering them towards the happy path.

- Bad/lacking open source tooling for portals, mocks, examples, validation versus OpenAPI & graphQL.

It all smells like unpolished MS enterprise crap with only internal MS & SAP adoption TBH.

Is there an article that explains OData? The articles I have seen did such a poor job I came away with the impression that it was a dead tech.