4 ms·
> This may be a stupid question, but what does "client/server" mean in this context? Not a stupid question at all, since terminology has been shifting over the
by noizejoy 6y ago
> This may be a stupid question, but what does "client/server" mean in this context?
Not a stupid question at all, since terminology has been shifting over the decades.
Back in the early 1990s, the original client/server generally meant all application code (logic and UI) on the client computer, and all the data on the server. So a very fat client.
Database stored procedures (i.e. some logic on the server) only arrived on the scene later during that time, because the original architecture of all code on the client caused performance nightmares. But don’t get me started on the trials and tribulations of early stored procedures. They often caused more project turmoil rather than smoothen things out. — Partly because they weren’t good languages yet, partly because of amplifying developer vs. dba conflicts.
- ptx 6y agoWithout any server-side logic, I suppose user permissions must have been handled entirely by the database, with clients connecting as different database users? Did row-level security already exist in some databases at that time? Otherwise this must have been quite limiting.
- ako 6y agoRow level security was usually handled through database views.
- gmfawcett 6y agoThere were alternatives to stored procedures for centralization. I remember RPC and CORBA being hot topics around that time. The tiered architecture was a thing before the Web.