3 ms·
I'm in agreement with GP; I work daily on code that does it the traditional way, and I use the "do as much as possible in SQL" in my own side projects, and it a
by lelanthran 4y ago
I'm in agreement with GP; I work daily on code that does it the traditional way, and I use the "do as much as possible in SQL" in my own side projects, and it always seems more maintainable to push off all the data logic into SQL.
> Do you have any good examples of this? Code bases that can be read?
I don't know of any projects that do this, but I do this for many of my side projects.
- septune 4y agoKeeping the business logic in-database was a major move in my career and a huge source of « well done sentiment ». My perfect combo today rely on golang as the (thin) API layer, querying data and making CRUD using plsql procedures, enforced by triggers and constaints.