Implementing a NoSQL and RDBMS compatible DAO
What would be the correct way to design a DAO which implementation is first going to be targeting a MS SQL database with a STAR model, but yet, business requirements specify the application must be flexible enough that it would be able to be migrated to a NoSQL database in the future if required. Which type of NoSQL, no idea…
Implementing a NoSQL and RDBMS compatible DAO
What would be the correct way to design a DAO which implementation is first going to be targeting a MS SQL database with a STAR model, but yet, business requirements specify the application must be flexible enough that it would be able to be migrated to a NoSQL database in the future if required. Which type of NoSQL, no idea…
Implementing a NoSQL and RDBMS compatible DAO
What would be the correct way to design a DAO which implementation is first going to be targeting a MS SQL database with a STAR model, but yet, business requirements specify the application must be flexible enough that it would be able to be migrated to a NoSQL database in the future if required. Which type of NoSQL, no idea…
Repository pattern vs DAO managing Entities
I am new to concepts like DAO, DAL and Domain Driven Design. In the end I want to decouple the persistence layer (mysql database) from my business objects and logic in a web application. I liked the DAO concept but I got stuck implementing it when I want to create a Business Object from database that has other entities associated with it (represented by foreign key in the db table).
Consuming a rest API that exposes nested objects
I have a series of nested objects, exposed over a REST API, like so:
What’s the correct approach to DAO layer in presence of ORM framework
I’m using JPA/Hibernate but probably it doesn’t limit question.