: Is there a good reason for implementing SolrCore as a Singleton? I'm going to sidestep the issue of wether there *was* a good reason for it, as well as the "does the singleton pattern make sense for the current usage" question and answer what i think is an equally significant question: "what are the implications of trying to change it now?" ... the biggest i can think of being that SolrConfig is also a static singleton, and a *lot* of code in the Solr code base would need to be changed to support multiple SolrConfigs ... and without multiple SolrConfigs, there really isnt' any reason to have multiple SolrCores.
-Hoss
