Post #903475
2026-01-24 17:01 UTC
so I’m revisiting “data oriented design” (because —who knew?— structs of arrays actually work really well with sqlx) and this quote jumped out at me:
“if you link your operations by related data, such as when you put methods on a class, you make it hard to unlink your operations when the data changes or splits, and you make it hard to split data when an operation requires it to be together for its own purposes”
Replies (1)
-
@isntitvacant@hachyderm.io 2026-01-24 17:07
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)