4 ms·
I know this is simple, but when you need to publish multiple versions of an API on a db, I don't see this as useful. It will only get in the way down the road o
by bluejekyll 11y ago
I know this is simple, but when you need to publish multiple versions of an API on a db, I don't see this as useful. It will only get in the way down the road of defining a strong API.
What you end up with in something like this is the data model is the API. Why not just expose SQL directly at that point? (Rhetorical question)
- yeukhon 11y agoThe psql client returns a format web client cannot consume. The translation to JSON for example is really important. The reverse (speak SQL) is also quite true. That being said, my observation (and my own project too is guilty of this) is that a lot of ORM users simply map their model almost 1-1 in the API response. An example would be returning a Book the json basically contains every column as keys.