3 ms·
Because schemas let you agree on the shape of the data without having to pull in applications to query things for reporting, analysis, etc. Additionally, forci
by kortilla 4y ago
Because schemas let you agree on the shape of the data without having to pull in applications to query things for reporting, analysis, etc.
Additionally, forcing things into a correct schema also protects you from a lot of data inconsistencies out of the box.
Finally, the dbms is going to be far better at JOINs than your application will. Nearly every web application needs JOINs at some point. Developers just don’t recognize what they are doing so they don’t realize what they are missing out on by doing it at the application layer.
- hardware2win 4y ago"At some point", but how much? I believe it is up to modeling skills Anyway - Schema slows development as hell, you need to maintain mapper layer between domain models and db models unless you model your system with anemic model mixed with tech stuff(db), but it is mess Additionally you deal with either stringly typed sql Or ORMs that require months of practice to be proficient even in c# which has LINQ