Skip to main content

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.

Required fields*

9
  • 6
    +!1 for mentioning the elephant in the room: the false assumption that one application uses just one DB and that one DB is used by just one app Commented Nov 30, 2016 at 10:02
  • 6
    @TulainsCórdova, I thought the elephant in the room here was Google's payroll system. :) Commented Nov 30, 2016 at 12:22
  • 9
    @Machado This is genius: "I'm willing to bet their payroll system runs on a relational database with lots of constraints." Commented Nov 30, 2016 at 12:27
  • 4
    It is also handy to have properly constrained databases as your application code is not ACID. Commented Nov 30, 2016 at 15:46
  • 4
    Just to emphasise the comment made by @MatthewWhited, it is not possible for applications to enforce some kinds of inter-row/inter-table constraints without performing locking and running extra queries. An RDBMS can do so at much lower cost. Commented Dec 6, 2016 at 9:35