[erlang-questions] REST interface to mnesia
Roberto Ostinelli
roberto@REDACTED
Wed Aug 31 20:18:33 CEST 2011
full-text indexing does come with a cost, sometimes related to write speed.
depending on how you want to balance these factors, and if text-search is
important (since it's your 8th point i'm not sure whether you can cross it
out or not), you may consider:
. riak with riak-search [as already suggested];
. solr (http://lucene.apache.org/solr/)
both are fast, have a JSON interface, and should answer your needs.
r.
2011/8/31 Joe Armstrong <erlang@REDACTED>
> On Wed, Aug 31, 2011 at 4:09 PM, Kevin Smith <kevin@REDACTED>
> wrote:
> > How important is queryability? Would you want to use qlc, SQL, MapReduce,
> or something else to write the queries?
>
> Not really. My order of priorities is:
>
> 1) Ease of install
> "working out of the box" and "a few files" is important
> I don't want lot's of files scattered all over the place
> Entire database in one blob is nice (like SQLite)
> should run forever on my machine without bothering me once installed
> 2) Easy management
> "it just works" - nice to have a web interface.
> 3) Low storage overhead - don't be too profligate with storage
> 4) Fast (ish) key-value storage. over 5K reads/writes/sec is fine
> 5) Crash resiliant
> 6) Can be controlled via a socket interface
> 7) indexing or secondary keys
> 8) full-text indexing
> 9) Relational queries less important - I'm kind of used to Key-Value
> queries
> and designing data structures round them
>
> /Joe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110831/a923154c/attachment.htm>
More information about the erlang-questions
mailing list