Post #2805314

and I’m thinking about this from the lens of your typical, run-of-the-mill CRUD-y HTTP REST API. as you know, this kind of API pushes you towards the “row-major” object model & away from “columnar” SOA. If I pick at “why”: it strikes me that the REST API is a narrow interface, and the effect of the narrowing is to widen the data representation in both directions. (put another way, the data is made more general to reduce its cardinality & make it more cache-friendly) the alternative being something like graphql, which widens the interface (while tunneling over a single http endpoint)