To add one more important aspect: performance. It should be possible to
order an evaluation license or something for a limited time (1-3
months). Put your data on the product (if possible) and measure the
"documents per second" while indexing and "queries per second" while
searching, for all your workloads. Compare that numbers to ES on your
favorite platform. Add your findings (ease of administration, network
latency, resource sizing challenges etc) Present the result to
management. Management always listens to technical staff when
performance is the issue - it is expensive to fix performance issues later.
Another more important one to kill every cloud-based app scenario is
data privacy but I'm not sure if your data is relevant to this topic.
Jörg
Am 24.05.13 01:10, schrieb Alex Roytman:
Thanks Tinou,
They have (or would have) google search (I guess appliance) in the
data center. so i do not think latency will be an issue. it is the
services it can provide, and integration I need to understand.
From very briefly going over google documentation my feeling is:
1.It is not free like Elasticsearch. The licenses may be quite costly
2.It is optimized for document and site indexing and searching and not
so much for structured data indexing searching, analytics and faceting
while elastic allows very easy mixing of both
3.It is a shrink wrap product which comes with GUI, administration and
is centered around searching for documents or web pages or emails plus
some metadata about them not structured data with 100^th of fields
with need to
4.It is not an open source or open platform - it is a shrink wrapped
solution with various connectors to pull data from various data sources.
a.It may be impossible to do something unless google baked it. For
example showing which fields got hits might not even be possible
b.It will be harder to integrate
5.Our product will be constrained to what google platform offers and
we will be bound to versions, licenses and upgrade schedule the IT
Shop has for the product
6.All documentation I found is about configuring and managing nothing
much about developing for it, executing complex custom queries etc.
7.I checked its user groups – they seems to be dormant unlike elastic
search. Not sure where one can get any support unless it is paid
8.Last not the least it will be starting development all over even if
it is possible to achieve the same with google
On Thu, May 23, 2013 at 7:03 PM, Tinou Bao <tinou.bao@gmail.com
mailto:tinou.bao@gmail.com> wrote:
I haven't used Google search. Briefly played around w/ Amazon
CloudSearch. One thing is latency that is probably applicable to
any cloud based solution. Within a data center you can update ES
and have near realtime updates. With AWS CloudSearch I remember it
does things in batches and there's also the latency of a network
request to Virginia.
On Thursday, May 23, 2013 12:06:02 PM UTC-7, AlexR wrote:
We have a really good pilot with ES and now infrastructure
people pushing google search on us because they have in on
their approved stack (and I bet to charge for licenses too)
What are the weaknesses of google search compared to ES?
Our application works with heavily structured data (large
number of small fields) and has lots of faceting and
analytics. Is google search any good with it structured
documents with many fields? Does it have it advanced faceting?
Does it allow fine grained control over indexing?
--
You received this message because you are subscribed to a topic in
the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/cbP2lp5UtZI/unsubscribe?hl=en-US.
To unsubscribe from this group and all its topics, send an email
to elasticsearch+unsubscribe@googlegroups.com
<mailto:elasticsearch%2Bunsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
