Hi Eugene,
Two facts which might be problematic for you using Elasticsearch as a
primary datastore. It does not support transactions, so its only atomic on
a single operation. It also has a limit with data availability for search.
It supports "near-realtime" search, so data will be not immediately
available for querying.
Michael
On Friday, March 29, 2013 4:48:59 PM UTC+1, Eugene Strokin wrote:
Hello,
I had a conversation with friend of mine about architectural choice for
his application.
Big amount of data needs to be queried in usual way (many reads, some
writes). Needs to be distributed, etc...
His idea was to have MongoDB working with ES in parallel to index subset
of the data from MongoDB.
I proposed to get rid of MongoDB completely since the subset is relatively
big, and store all the data just in ES and use it as DB as well as text
search engine.
So, ES would be NoSQL DB with text search features, which is actually a
super set of MongoDB (feature wise).
This way the application would be simpler, have less failure points,
etc...
We both are not experts in MongoDB, nor could call ourselves experts in
ES, but more like experienced users. So, to dispel all doubts, could
someone who has experience in both fields propose some scenarios where
usage of MangoDB in conjunction with ES is justified?
For now, I'd say, if there is ES in the house, no need to bring MongoDB in.Thanks in advance,
Eugene
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.