Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    Database first design fails the high hanging fruit concepts of unit testing and code reuse. If neither is a concern, it's a quick way to get stuff done. Also, see something like dba.stackexchange.com/questions/76973/… . There's a general consensus in there against complex queries. Commented Jul 12, 2018 at 22:54
  • 2
    I generally agree with your approach, but I can't give it as an answer to all situations as every one is different. Given my view that all business is applying process to data, I'd certainly get my DB correct first. I also agree that intensive data processing is best handled on the DB (mostly, but not always). Trivial lookups and the odd OLTP type operation I'd use ORM but when it gets bulky I'll drop back to view/SP. So not an answer, because there is no one correct one. This is what architects are for. Commented Jul 13, 2018 at 1:16