3 ms·
Your business is the database. Models matter. Anyone who wants "database neutrality" (least useful common denominator), vs leveraging the awesomeness of pgsql,
by specialist 10y ago
Your business is the database. Models matter.
Anyone who wants "database neutrality" (least useful common denominator), vs leveraging the awesomeness of pgsql, mssql, oracle, should just use flat files. Or mysql.
- UK-AL 10y agoYou can leverage whatever database feature you want, just a long as you do it in the database adapter/gateway. I write mine in raw sql normally.
- specialist 10y agoVersus in situ (eg stored procedures)? I currently agree. There was a time when the database engine was the "app server". Before client/server & ODBC. I miss those days. That strategy is overdue for a comeback.
- UK-AL 10y agoMy raw sql can call out to stored procedure if that's the best tool for the job. A database is a perfectly good application core, if you application primary about creating/updating/deleting records. If your application is business workflows, and complicated business logic. Then this is something to be considered.
- pmart123 10y agoGood to see I'm not crazy! I think this can be easier than maintain, and with tools like Datagrip now, seems to make a lot of sense. Coming from the data science side, I observed many talented people spending time on projects like https://github.com/cloudera/ibis https://github.com/cloudera/ibis to abstract SQL into something that I often thought was more verbose, less literal and less portible in reality.
- vardump 10y agos/mysql/sqlite Almost foolproof.
- jlg23 10y ago> Your business is the database. Models matter. If you tie your model to your database, you might be out of business sooner that you think. Just ask any of the oracle customers who paid $$$ to migrate away from that license fee sinkhole. > Anyone who wants "database neutrality" (least useful common denominator), vs leveraging the awesomeness of pgsql, mssql, oracle, should just use flat files. Or mysql. Alternatively, simply invest a little bit more time into proper design and implementation. In one of my products I am "leveraging the awesomeness of pgsql" but switching to another storage engine is still a matter of one or two hours. After all, it's only about 200 lines of code: The connection itself and the adapters for the query engine (and no, it's not loosely coupled - it's strongly typed and my compiler inflects on the model and the constraints imposed on it by the storage backend).