Hello!
Well, I'm a brand new CouchDB user, still in learning stage but reading as
much as I can. I'm a bit confused about how people have been using CouchDB
as primary back-end, and how common back-end tasks are implemented (if they
are) on it. I've read a lot about its functionalities but I'm still
confused about how they relate to traditional back-end apps, for example:
- *Document CRUD control:* I know there are design documents which make
it possible to create validation documents, but the code is stored on
database. How do you control the lifecycle of the code (track it with a
VCS, code, test, debug, etc.)?
- Also, is there any way to make *CouchDB read a view code from file
system instead of a document?*
- *Access control level:* there are user/password authentication,
with optional roles usage, but how can I store "private" documents - like
documents that are accessible for some role?
- *"Cron tasks":* is there any way to implement tasks that need to be
executed frequently, like data integrity, math operations, cache
invalidation, or some kind of task that really need to be done periodically?
- What are the *best practices for CouchDB based development?* And if
there's some, why its not on CouchDB Docs yet? :)
I believe there must be some very-beginner tasks, so if you can share links
for reading I would appreciate.
Thank you, guys! CouchDB is awesome!
--
Joel Wallis Jucá
joelwallis.com
