3 ms·
I started my career out writing database applications. Every aspect of those applications were schema-driven, and I would generally would try and solve problem
by jdonaldson 8y ago
I started my career out writing database applications. Every aspect of those applications were schema-driven, and I would generally would try and solve problems at a schema level (e.g. for rendering/presentation, etc.)
In application development, it's gotten very popular to ignore the data storage component of application design, or at least defer it to the last possible moment. React et al take things even further by requiring their own modeling logic.
As many here would agree, relational dbs never went away. But for some reason folks stopped trying to push the envelope with schema-driven application development. I kept expecting to see iterations of schema-driven design and layout system (using inputs derived from table fields, etc). What we got instead is this ORM business. Is there a schema-first tooling community that I'm unaware of?
- haolez 8y agoI'm not sure if this fits your bill, but you can go pretty far into application logic by combining PostgreSQL and PostgREST (https://postgrest.com/ https://postgrest.com/).
- jdonaldson 8y agoI think that's a great example!