逻辑的分离:搜索、数据库和应用-SeparationofLogic:Search,Database,&Application

I'm trying to decide how I want to split up my logic.

我正试图决定我该如何打破我的逻辑。

I'm placing my main business logic in Node.js/Express, and I had been using Mongo for my database. This works great, but now I need to implement a really powerful search system, as search is one of the most important features of my site. At first I was very amazed at the lack of support and integration that Mongo and Couch offered, but then I realized I was trying to get a database to do something it wasn't made for.

我把我的主要业务逻辑放在Node。js/Express，我一直在使用Mongo作为我的数据库。这很有用，但是现在我需要实现一个非常强大的搜索系统，因为搜索是我的站点最重要的特性之一。起初我对Mongo和Couch提供的支持和集成的缺乏感到惊讶，但后来我意识到我想要一个数据库来做一些不是为它而做的事情。

Now I'm looking at using Solr or ElasticSearch, but its beginning to seem that these are capable of even doing some or most of the queries that Mongo can do, as long as I index my documents correctly (and by their nature, I will be indexing pretty much every property of every document). So that said, I'm thinking maybe I should just use something dead simple, like Redis, and rely on a powerful search tool like Solr/ElasticSearch instead.

现在我看着使用Solr或ElasticSearch,但是它开始看起来,这些甚至有能力做一些或大部分查询Mongo能做的,只要我索引文件正确(从本质上说,我将每个文档的索引几乎所有属性)。所以说，我在想也许我应该用一些简单的东西，比如Redis，然后依靠一个强大的搜索工具，比如Solr/弹性搜索。

Does this seem like a wise choice? Also, why are there no Nodejs modules for Solr, Lucene, or ElasticSearch?

这看起来是个明智的选择吗?另外，为什么没有Solr、Lucene或ElasticSearch的Nodejs模块呢?

1 个解决方案