And why maybe not?

Of-course the main focus of this website is to show to benefits of using Solarium. However, it’s probably just as important to also tell you what not to expect of Solarium and when you might be better of using another solution.

What Solarium doesn’t have

  • User interface components. It’s very hard to find a generic solution for things like faceting and result browsing. It might be added in some form in the future, but for now you need to implement this yourself in your application.
  • 100% of all available Solr functionality. The most used features have been implemented, but be sure to check for the features you need. You can however always add new functionality yourself as Solarium uses a flexible structure. And you can also manually set custom request params if you need to.
  • The ability to fully automate the use of Solr, you still need decent Solr knowledge to use it.

When not to use Solarium?

  • If you need a library with a very small footprint in number of files and total size. The Solarium library has dozens of files. Of-course the files are only loaded when used, but it’s way bigger than some of the more basic solutions available.
  • If you have a very simple use case the complex model might be overkill. However, in many cases a simple use case will grow more and more complex over time so Solarium might still be justified. Also, while Solarium offers a lot of features, the basic API is not complex.
  • If you are tied to a PHP version below 5.2. Solarium is only tested against PHP 5.2+. For 5.0 and 5.1 releases it might just work. But everything below PHP5 won’t for sure.
  • If you have any issues with the license, though thats highly unlikely as Solarium uses a very permissive license.