Reasons for setting up standalone solr server when using Sunspot in production?

Question

I am trying to figure out why we shouldn't use sunspot gem by itself in production environment?

Most people recommend setting up a standalone solr service such as jetty+solr or tomcat+solr.

Can anybody explain what are the cons of running as an embedded service?

score 0 · Answer 1 · edited May 23 '17 at 11:56

0

Sunspot is perfectly usable in production. You have to set up your own Solr server, though, which I think is what you're talking about. For that, there's an already answered StackOverflow question that I think will help you get started.

edited May 23 '17 at 11:56

Community

1
1

answered Jul 19 '12 at 16:24

Veraticus

15,944
3
41
45

I mean why we can't go with embeded **solr** in production – Volodymyr Jul 20 '12 at 08:02
1

@Vladimir I think this [wiki page](http://wiki.apache.org/solr/EmbeddedSolr) should give you a reasonable answer. – javanna Jul 20 '12 at 14:27

score 0 · Answer 2 · answered Nov 01 '12 at 19:37

0

This link has some info: http://outoftime.github.com/pivotal-sunspot-presentation.html It also says it should be on its own machine.

answered Nov 01 '12 at 19:37

konyak

10,818
4
59
65

Reasons for setting up standalone solr server when using Sunspot in production?

2 Answers2