These are chat archives for jdubray/sam
If you have a single system of record (aka a monolith), I have a great API design for you! it's call SQL (no literally executing a SQL statement, but close enough).
could you explain this a bit more?
"Static" people don't get the power of dynamic/extensible data structures
haha, I like to be called "static", but pls keep in mind that static+extensible is possible though with several typed-first languages
I get the minimum structure possible (when I am in control of both ends) and let SQL do the heavy lifting with column name matching my JSON conventions.
@jdubray so you just have one endpoint on the backend where you post a query-like datastructure that is then transformed to sql, something like that? I would really love to completely get rid of any transport problematic and call something on the front that results on whatever happening so that something is called on the backed. I really don't need to bother with all the REST/json wiring... something like the RMI of modern frontend/backend world :)