Revision as of 11:35, 1 January 2022 edit Akrowitz (talk \| contribs) 83 edits m Provide a link for 'persistence' ← Previous edit		Revision as of 21:44, 22 November 2022 edit undo Forresthopkinsa (talk \| contribs) 35 edits Hypothetical use scenario: inappropriate second-person Next edit →
Line 24: == Hypothetical use scenario == {{inappropriate person\|section\|you}} Imagine a situation where you own a successful company that has received contracts to develop an application for 2 different clients. The specifications for the application are nearly identical for the 2 clients. Both clients manage data using SQL databases, but one company uses a proprietary database and the other uses an open source alternative, which implies that your application's [[persistence layer]] will need to be implemented in 2 different ways. Further, as new clients arise, additional implementations may be needed. In this case, using the Data Access Object pattern would ensure the right amount of abstraction and encapsulation required to access any of the varying backend databases.

Data access object: Difference between revisions