|
Why
Why DBR
IntroductionIn many software applications, a database serves as the backbone. Interaction with the database comprises a substantial portion of the codebase. Traditionally, relational databases are accessed through a very lightweight communication layer. The application code must generate SQL to be executed, and process the response directly. For many applications, this is satisfactory. Once this application becomes more and more complicated, this direct method becomes more and more problematic. One faces several problems, including SQL injection attacks, value translation, and frequently repeated boilerplate code. When dealing with a large codebase, numerous repetitions of various database calls could start to add up to a whole lot of boilerplate. Therefore, a small reduction in code volume and complexity of these database calls would end up having a tremendous effect. Any simplification to the interface of the DB library would be multiplied by hundreds or even thousands of occurrances throughout the code. It would Increase readability, decrease overall complexity as well as bugs, and potentially quicken on-boarding of new team members. For some insight into the decision making process that led to DBR, See DBLibraryComparison Details |