Dao pattern is a classic with relational database. Now i need to implement a couchbase tier, and I wonder what would be the best design pattern for key/value access.
Have you some experience to share about this kind of design patterns?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Dao pattern is a classic with relational database. Now i need to implement a couchbase tier, and I wonder what would be the best design pattern for key/value access.
Have you some experience to share about this kind of design patterns?
You can use the DAO pattern for any kind of persistent storage mechanism, be it relational database, filesystem, text document, Couchbase, etc. The DAO layer is very generic and it does only one thing: converts your runtime objects to and from their persisted counterparts.
So for a relational database, your DAO layer takes Java objects, converts them to tables and rows and stores them in the DB using SQL; and vice-versa. For Couchbase, your DAO layer would take Java objects, convert them to JSON documents, and store them in the DB using HTTP. Same pattern, just different details.
The advantage of the DAO pattern is then readily evident: if next year, some amazing new storage mechanism comes out that’s twice as good as Couchbase and runs circles around SQL databases, all you need to change is your DAO layer. The rest of the application doesn’t even know or care.