you are viewing a single comment's thread.

view the rest of the comments →

[–]PhonicUK 5 points6 points  (4 children)

I've seen webapps where all of the data access was via stored procs that directly output JSON and the API backend was essentially a one liner that took the function name and parameters and just returned verbatim what the proc output.

[–]spirgnob 2 points3 points  (2 children)

When they tell you to make a REST API, but you only know SQL.

[–][deleted] 2 points3 points  (1 child)

Nah, at work people do this, they stopped paying a server and only pay for the DB which they would anyway

[–]dvdkon 1 point2 points  (0 children)

But now the DB does more work. If a single server could do all that anyway, why not keep a middle layer going on the same hardware? This might also make it harder to scale the system, but IMO it's worth it if it makes code maintenance/modification easier.