News for hackers. Stuff that matters.
Re:Full-Text Search in Django with PostgreSQL by yeukhon on Saturday January 06, 2018 @02:17PM (#16086933)
> Why not just run ElasticSearch on a single instance then ?

Sorry, I am not sure why you brought up a single instance. If you run on a single instance, you lose half of the benefits of ES which is trying to be highly available.

If we have an index which does not need any backups, single instance is fine, but for most people single instance is not an option. Furthermore, if one is already struggling with 3-4 nodes, how helpful is single instance?

Re:Full-Text Search in Django with PostgreSQL by threeseed on Saturday January 06, 2018 @02:25PM (#16086967)
I brought up single instance since you suggested using a SQL database most of which don't support a distributed deployment in the same way ElasticSearch does.

My point was merely that ElasticSearch scales from very small use cases to very large ones. You don't have to setup a cluster. And that using your SQL database isn't going to be significantly easier to manage.

Re:Full-Text Search in Django with PostgreSQL by moe on Saturday January 06, 2018 @07:03PM (#16088231)
> SQL database isn't going to be significantly easier to manage.

A SQL database doesn't run out of memory and crash when you add documents to it "too fast". ElasticSearch does.