If you need to search via the Hibernate API, then use hibernate search.
If you need a scaleable HTTP (REST) then solr may be the way to go.
Also, i don't think hibernate has anything like the faceting / complex
query stuff etc.
On Dec 29, 2009, at 3:25 PM, Márcio Paulino wrote:
Hey Everyone!
I was make a comparison of both technologies (SOLR AND Hibernate
Search) and
i see many things are equals. Anyone could told me when i must use
SOLR and
when i must use Hibernate Search?
Im my project i will have:
1. Queries for indexed fields (Strings) and for not indexed Fields
(Integer,
Float, Date). [In Hibernate Search on in SOLR, i must search on
index and,
with results of query, search on database (I can't search in both
places ate
same time).]
I Will Have search like:
"Give me all Register Where Value < 190 And Name Contains = 'JAVA' "
2. My client need process a lot of email (20.000 per day) and i must
indexed
all fields (excluded sentDate ) included Attachments, and
performance is
requirement of my System
3. My Application is multiclient, and i need to separate the index by
client.
In this Scenario, whats the best solution? SOLR or HIbernateSearch
I See SOLR is a dedicated server and has a good performance test. I
don't
see advantages to use hibernate-search in comparison with SOLR
(Except the
fact of integrate with my Mapped Object)
Thanks for Help
--
att,
**********************************************
Márcio Paulino
Campo Grande - MS
MSN / Gtalk: mcopaul...@gmail.com
ICQ: 155897898
**********************************************
