Elasticsearch as DB or Elasticsearch over MongoDB

Question

not sure that question belongs to this "stack" but here we go...

My use case is to provide a full text search on a large amount of data. New data is being added all the time.

I know Elasticsearch will search fast quickly, but I don't know if Elasticsearch as a NoSQL database (to simply store the data) will have better performance compared to storing the data in MongoDB and index the MongoDB using Elasticsearch.

Thanks in advance!

Some answers to read: stackoverflow.com/questions/12723239/… + stackoverflow.com/questions/29538527/… — Val
– Val, Commented Jan 5, 2018 at 5:45

pkhlop · Accepted Answer · 2018-06-04 21:45:15Z

5

tl;dr It is perfectly good to use it as primary storage if you don't need ACID compliant database. Do backups.

There is an answer on this often asked question from Elastic team

Some key points first:

We do not advertise Elasticsearch as a primary data store but many customers are using it as a primary data store.

Elasticsearch is an eventually consistent, near-realtime storage engine.

Elasticsearch is not ACID compliant like a database.

This page has current status of issues you can face

It also depends on other features you have in your system.

I have experience using Elasticsearch as primary data storage on high traffic web site for several years. It works very good.

edited Jun 4, 2018 at 21:45

answered Jan 4, 2018 at 23:04

pkhlop

1,8443 gold badges19 silver badges24 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Elasticsearch as DB or Elasticsearch over MongoDB

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related