Elastic Search as a primary data store

Is there a reason to not use ElasticSearch as a primary data store for an
application?

Thanks
DK

--
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.

Hi,

No. Although, to answer this properly, one would need more details on your
use-case.

Generally, if you want to use ES anyway, it's a good idea to make it your
only data store. Because there would be fewer moving pieces.
On Jun 11, 2013 8:22 AM, "David Kullmann" kullmann.david@gmail.com wrote:

Is there a reason to not use ElasticSearch as a primary data store for
an application?

Thanks
DK

--
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.

--
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.

Interesting, really interesting.
I am new to ElasticSearch (less than 1 month) but I am learning a lot in
this list.

What I have seen on the web is that people are using CouchDB+ElasticSearch,
or MongoDB+ElasticSearch, and they say that it is worth paying the price of
more moving parts.

Why so?
What is the difference between this options? I cannot see that clearly.
May one of the really knowledgeable explain something about this?

Thanks in advance.

2013/6/14 Radu Gheorghe radu.gheorghe@sematext.com

Hi,

No. Although, to answer this properly, one would need more details on your
use-case.

Generally, if you want to use ES anyway, it's a good idea to make it your
only data store. Because there would be fewer moving pieces.
On Jun 11, 2013 8:22 AM, "David Kullmann" kullmann.david@gmail.com
wrote:

Is there a reason to not use ElasticSearch as a primary data store for
an application?

Thanks
DK

--
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.

--
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.

--

Fátima Castiglione Maldonado
castiglionemaldonado@gmail.com

                 ____
               ,'_   |

|||
<
) .------.
-----------,------.-' ,-'-.
| | | ,' . ,' | | ,'.
| ,-' |
/
,'-' .---.|
_____
.--' -----. | _____________________ -. ----- | | ___| | | \ ,- \ | | ___| |===========================((|) | | | | | | _____________________/- / |
--._ -----' | _________________,-' ----- |.-._ ,' __.---' | /
| -. | \ /. | | . ,' | | |. ,'
_____,------------------. -._ _,-' <___________________________)------'
| | |
`.
___|

=================================

--
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.

I have experience using ElasticSearch as primary DataStore for my public website. I have had no issues what so ever. Had some problems with real-time availability but by refreshing at certain points I was able to come around this issue.

/James

The answer depends.

Although Elasticsearch is not a store but an index, it can be used as a
store, for many use cases. Without defining the use case, it is
impossible to give a solid answer.

If you examine the techology stacks of CouchDB, MongoDB, Elasticsearch,
you will find what you need to know for your personal decision because
only you know best what data you have and how you want them to get
processed.

Maybe it helps to rethink the question about "primary data store" a
little bit. With primary data store, many people associate a SPOF where
all the writes go to first, often cotnrolled by transactional
operations. Such a SPOF does not exist in ES at all.

These questions may help to get a bigger picture. CouchDB, MongoDB,
Elasticsearch give all different answers to them.

  • do you want to use Lucene features? Analyzers? Facets?

  • do you want scalable indexing and search with shards and replicas?

  • do you have full-text documents, or data in hierarchical trees, or
    graph nodes?

  • do you want polyglot persistence? do you want to use data persistence?
    Or object persistence?

  • do you want multi tenancy? Does each client bring his own data and
    method/technlogy of indexing/searching?

  • do you have fast moving small pieces of data? do you want fast writes
    (updates)? Can you rebuild indexes often, can you incrementally push
    updates? Do you modify whole indexes or single documents or values in
    fields of a document?

  • do you need robust backup/restore?

  • and much more (e.g. ease of setup/configuration, ease of
    administration, ease of scaling, ...)

To sum up some limits of ES, there is no support for participating in
transcactional operations, writes are much slower than reads, and there
is no support for large streaming content and blobs because it is built
on JSON and HTTP REST (some people want to store some binary GB sized
blobs in a single field which is rarely a suitable use case for a search
engine).

Jörg

Am 15.06.13 06:40, schrieb Fatima Castiglione Maldonado 发:

Interesting, really interesting.
I am new to ElasticSearch (less than 1 month) but I am learning a lot
in this list.

What I have seen on the web is that people are using
CouchDB+ElasticSearch, or MongoDB+ElasticSearch, and they say that it
is worth paying the price of more moving parts.

Why so?

--
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.

Oh, thanks.
Very good questions.

2013/6/15 Jörg Prante joergprante@gmail.com

The answer depends.

Although Elasticsearch is not a store but an index, it can be used as a
store, for many use cases. Without defining the use case, it is impossible
to give a solid answer.

If you examine the techology stacks of CouchDB, MongoDB, Elasticsearch,
you will find what you need to know for your personal decision because only
you know best what data you have and how you want them to get processed.

Maybe it helps to rethink the question about "primary data store" a little
bit. With primary data store, many people associate a SPOF where all the
writes go to first, often cotnrolled by transactional operations. Such a
SPOF does not exist in ES at all.

These questions may help to get a bigger picture. CouchDB, MongoDB,
Elasticsearch give all different answers to them.

  • do you want to use Lucene features? Analyzers? Facets?

  • do you want scalable indexing and search with shards and replicas?

  • do you have full-text documents, or data in hierarchical trees, or graph
    nodes?

  • do you want polyglot persistence? do you want to use data persistence?
    Or object persistence?

  • do you want multi tenancy? Does each client bring his own data and
    method/technlogy of indexing/searching?

  • do you have fast moving small pieces of data? do you want fast writes
    (updates)? Can you rebuild indexes often, can you incrementally push
    updates? Do you modify whole indexes or single documents or values in
    fields of a document?

  • do you need robust backup/restore?

  • and much more (e.g. ease of setup/configuration, ease of administration,
    ease of scaling, ...)

To sum up some limits of ES, there is no support for participating in
transcactional operations, writes are much slower than reads, and there is
no support for large streaming content and blobs because it is built on
JSON and HTTP REST (some people want to store some binary GB sized blobs in
a single field which is rarely a suitable use case for a search engine).

Jörg

Am 15.06.13 06:40, schrieb Fatima Castiglione Maldonado 发:

Interesting, really interesting.
I am new to ElasticSearch (less than 1 month) but I am learning a lot in
this list.

What I have seen on the web is that people are using
CouchDB+ElasticSearch, or MongoDB+ElasticSearch, and they say that it is
worth paying the price of more moving parts.

Why so?

--
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.comelasticsearch%2Bunsubscribe@googlegroups.com
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.

--

Fátima Castiglione Maldonado
castiglionemaldonado@gmail.com

                 ____
               ,'_   |

|||
<
) .------.
-----------,------.-' ,-'-.
| | | ,' . ,' | | ,'.
| ,-' |
/
,'-' .---.|
_____
.--' -----. | _____________________ -. ----- | | ___| | | \ ,- \ | | ___| |===========================((|) | | | | | | _____________________/- / |
--._ -----' | _________________,-' ----- |.-._ ,' __.---' | /
| -. | \ /. | | . ,' | | |. ,'
_____,------------------. -._ _,-' <___________________________)------'
| | |
`.
___|

=================================

--
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.