How do you architect the CF backend model w/ NoSQL that are simple, 
flexible, efficient and clean?

Since NoSQL doc has no fixed schema like SQL row, it doesn't really fit well 
with Objects which are rather static. Therefore the typical Bean+DAO+Service 
OOP architecture doesn't seem to fit well.

I'm thinking of using plain old Struct's, but then I cannot add behavior 
onto it and it's going to make the whole project very procedural, which may 
not be a bad thing?

However, if I just use plain old struct, the DB implementations is leaked 
everywhere including the View layer...

Or... shall I translate the array's into CF's Query object for the View 
layer?

Comment? Idea? Suggestion?

Thanks!


p.s. also asked here: 
http://stackoverflow.com/questions/4622121/nosql-with-coldfusion-beanservicedao-oop-or-good-old-array-struct-procedur

-- 
You received this message because you are subscribed to the Google Groups 
"CFCDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/cfcdev?hl=en.

Reply via email to