java - What is wrong with embedding solr - Stack Overflow
The embedded server is recommended when you need a simple solution that is not distributed. For example when writing small unit and integration tests you might want to have a special Solr instance with special configurations such like using RamDirectories and not writing changes back.
This is also true for development databases. I always use in-memory databases not writing back to file loading a preset scenario (I also use for acceptance and integration tests). This way you have a speed advantage on restarting application and doing regression tests. It is a difference if your server is up in one second or in 10 seconds and that is what you can Achive. If your tests run slowly you are slowed down when it comes to test driven development.
Also another thing is if you need a dedicated Solr server instance or require cloud functionality you can easily switch from using an embedded server to a stand alone server. This is just some lines of code and you are done.
So if you do not know if you need a dedicated server just start with the embedded version and enjoy simplified configuration and setup and a minor performance increase. Once you need a stand alone server, just change some lines of code and the rest stays the same.
Read full article from java - What is wrong with embedding solr - Stack Overflow
No comments:
Post a Comment