You may cook-up whatever storage you want. The core zotonic parts are
tightly coupled with postgres, but any custom models you write are
free to use whatever storage suits you.
The model is a "water proof" wall between your use of the data, and
the storage in use. You access the model from your templates (or other
erlang code), and the model is responsible for storing and retrieving
the data.
Some functionality (search) may be at a loss if the data isn't stored
according to zotonics data model in postgres, but that may as well be
a non-issue (I'm not very familiar with mod_search, so it's more of a
hunch, Arjan or Marc will be able to give a more precise answer).
I wouldn't hesitate to use zotonic for any project that needs a web presence.
//Andreas
2011/8/12 Juan Jose Comellas <jcom...@gmail.com>:
You can add your own search observers and perform searches on your own data store.
This enables you to use m.search with your own models.
Check mod_search how to observe the search notifications.
It might also be possible to store your JSON documents in a special resource category (or categories).
Then you can add additional admin templates to edit or view the contents of your documents.
And you can easily mix/match between the different resources in your system, enabling atom feeds, search, presentation etc.
You can also hook the pivot routines to get a good full text index of your documents.
This is what I mostly do when I receive documents.
- Marc