Timeline for Database agnostic DAO (NoSQL + SQL)
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 20, 2021 at 8:44 | vote | accept | Harshit | ||
| Feb 20, 2021 at 8:44 | vote | accept | Harshit | ||
| Feb 20, 2021 at 8:44 | |||||
| Jul 25, 2019 at 9:16 | vote | accept | Harshit | ||
| Feb 20, 2021 at 8:44 | |||||
| May 28, 2019 at 11:46 | comment | added | Kayaman | @RobertHarvey but then we're going up in the layer hierarchy (at least if we're following traditional architectures). If the point is to concentrate on the data layer, i.e. deep in the core, then it's easy to get into the situation described by Robert. Just try shoehorning the JDBC abstraction layer into supporting a NoSQL database, and it becomes obvious. Upper layers are of course easier to model in a storage agnostic way, as you said. | |
| May 26, 2019 at 20:28 | comment | added | Robert Harvey | I disagree with you to a certain extent. While you certainly could default to some trivial CRUD interface, you don't have to. You can build a database-agnostic abstraction layer (such as a Service Layer) that provides sensible, business domain-related access methods while still taking advantage of whatever advanced features the database (and its companion data access layer) provides. | |
| May 26, 2019 at 7:30 | history | edited | Robert Bräutigam | CC BY-SA 4.0 |
added 118 characters in body
|
| May 26, 2019 at 7:23 | history | edited | Robert Bräutigam | CC BY-SA 4.0 |
added 118 characters in body
|
| May 26, 2019 at 7:18 | history | answered | Robert Bräutigam | CC BY-SA 4.0 |