Posted by Jim Cheesman on Mar 22, 2011; 4:38pm
URL: https://discuss.orbeon.com/Architecture-question-tp3394205p3396973.html

Thanks Tom, I'll check out Solr. Basically most of the data should be fairly static - it's user registration data that'll will be updated every now and then, but shouldn't be that often. Some kind of indexing / BI style tool could be ideal.

Cheers,
Jim


On mar, 2011-03-22 at 03:43 -0700, Tom Grahame wrote:

For what it's worth, you might consider an XForms (Orbeon), REST, XML (Exist,
Fedora Commons) solution for creating and storing data. Then separate away
the searching of that data using  http://lucene.apache.org/solr/ Solr , my
project has had good success with that tool.

I'd suggest the key is in being certain in which part of your XML document
life cycle the high usage/performance hits will be.

Tom

--
View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Architecture-question-tp3394205p3396010.html
Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.

plain text document attachment (message-footer.txt)

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
OW2 mailing lists service home page: http://www.ow2.org/wws

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws