RedBeanPHP vs Solr
When comparing RedBeanPHP vs Solr, the Slant community recommends RedBeanPHP for most people. In the question“What are the best PHP ORMs?” RedBeanPHP is ranked 1st while Solr is ranked 8th. The most important reason people chose RedBeanPHP is:
It requires basically nothing except database credentials making it awesome to use.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Zero configuration
It requires basically nothing except database credentials making it awesome to use.
Pro Great for rapid development/prototyping
Since it employs a strategy of zero configuration, it can create all required databases and tables on the fly. Making it a great ORM to use when quickly prototyping a product.
Pro SQL extensions
Offers additions to SQL that makes querying very easy.
Pro CLI applications can be written in no time
You can generate CLI applications in no time as well.
Pro Customizablity
A key differentiator of Solr is the level of customizability the SearchComponent feature provides.
SearchComponent provides the developer astonishing flexibility in the way search queries are assembled and executed. At the time of writing, there does not appear to be a ElasticSearch equivalent of SearchComponent. source
Whilst ElasticSearch has a number of plugin-points there doesn't appear to be an equivalent of Solr's SearchComponent that enables you to modify the workflow of existing API endpoints.
Pro Open source
Pro Stats component
Solr allows to view average, standard deviation, maximum, minimum, sum of squares of a particular numeric field. It also allows faceting of that numeric field based on the value(s) of other fields.
Pro Results grouping
Solr allows you to group search results. Results can be grouped by:
- Field Value
- Query
- Function Query
You can also collapse multiple results with the same field value down to a single result.
Pro Decision tree faceting
Solr has a faceting feature called pivot facets or 'decision tree facets'. Pivot facets enable you to calculate facets inside a parents facet, for example pivoting on 'size' than 'color' returns 'color' facet counts for each 'size' facet
Pro Local params
Solr has a great feature that enables you to use LocalParams to perform more advanced faceting. They provide a way to "localize" information about a specific argument that is being sent to Solr. In other words, LocalParams provide a way to add meta-data to certain argument types such as query strings. From the Solr Wiki:
LocalParams are expressed as prefixes to arguments to be sent to Solr. For example:
Assume we have the existing query parameter
q=solr rocks
We can prefix this query string with LocalParams to provide more information to the query parser, for example changing the default operator type to "AND" and the default field to "title" for the lucene query parser:
q={!q.op=AND df=title}solr rocks
Pro SpellChecker
Solr allows has the functionality to check and correct spelling mistakes in search queries. The three main implementations are:
- IndexBasedSpellChecker
- WordBreadkSolrSpellChecker
- DirectSolrSpellChecker
Cons
Con Not suitable for existing projects with a custom database
Since RBP has a no-config approach, it enforces pretty strict database conventions. This does not make it a good ORM for an existing custom database.
Con Doesn't empty the legacy ORM columns from the table, like user and instead only adds user_id to it
Con General missing features
Solr is currently missing the following general features:
- Per-doc/query analyzer chain
- Support for nested documents
- Support for multiple document types per schema
- Ability to modify document scores with custom scripts
- Equivalent to Elasticsearch's percolation
Con Missing some useful features for cloud distribution
Solr is currently missing the following features that are useful when managing a distributed system:
- Automatic shard rebalancing
- Ability to re-locate shards and replicas on demand
- Ability to change the schema without restarting the server
- Ability to search across multiple indexes.