Skip to main content

Timeline for Database agnostic DAO (NoSQL + SQL)

Current License: CC BY-SA 4.0

13 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 27, 2019 at 7:50 comment added Laiv You will have to look for a good reason to provide your application with so much abstraction. In the first place, NoSQL and SQL engines are not interchangeable. this should be enough for you for giving up on trying to make your code ultra agnostic. The adequate engine to use is dictated by the business, not by tastes or fashions. Abstracting DB from the business is a must have. The question is how much abstraction do we need? On the other hand, supporting joins is less of the concerns here. Atomic transactions should concern you more.
May 26, 2019 at 12:14 answer added Steve timeline score: 1
May 26, 2019 at 7:18 answer added Robert Bräutigam timeline score: 8
May 26, 2019 at 6:03 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Apr 25, 2019 at 18:02 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Mar 26, 2019 at 18:06 comment added Robert Harvey Create a JSON API that supports the operations you need. Under the hood, you can implement that API however you like. Some features of the API may not work in both cases, and that's OK.
Mar 26, 2019 at 17:50 answer added Michał Kosmulski timeline score: 0
Mar 26, 2019 at 17:13 answer added candied_orange timeline score: 0
Mar 26, 2019 at 16:55 review First posts
Mar 26, 2019 at 18:29
Mar 26, 2019 at 16:50 history asked Harshit CC BY-SA 4.0