Yes, Let's say that you wan to represent a pie graph with some short of aggregated data in it extracted from elasticsearch. Instead of writing the query in javascript or having it client side in the code we need something like a simple call of a get API for instance getMyPieData() from another service and get the data to represent that information.
If we let elasticsearch to do that we may want to use search templates: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-template.html#pre-registered-templates if we want to as well cache that query we may use elasticsearch query cache: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-shard-query-cache.html#index-modules-shard-query-cache That is what elasticsearch more or less provides for my use case afaik. My question is if there is something else that I can do to cache and "hide" my queries apart from the over-mentioned solutions which make me bound to elasticsearch(some separate module, technology etc. based on best practises), while in another case I might want to change elasticsearch with something else and still not affect my frontend code, or more important not to constantly hit elasticsearch for those data. I'm trying to first verify that I will not reinvent the wheel and build my own solution Thank you again On Friday, 2 January 2015 17:04:59 UTC+2, Thomas wrote: > > Hi, > > I wish everybody a happy new year, all the best for 2015, and in > continuation of the great success of ES, > > In our project we intend to create a simple webapp that will query > elasticsearch for insights. We do not want to directly query elasticsearch > for two reasons: > > - security > - avoid boilerplate query code and to be able to decouple it > > What is the best way to achieve that? We are currently evaluating building > the frontend in python/django project. has anyone faced similiar task and > is it possible to share some thoughts? > > In other situations NGinX was a solution for security, but for avoiding > having all the boilerplate query code in client side (e.g. in javascript) > what is the most well established way? > > Finally, there are cases were some caching may be needed to avoid hitting > elasticsearch constantly for the same data, how is this tackled? We need to > build our own module to do all these? > > thank you in advance > > Thomas > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2ba94df5-7f54-4ec3-87f5-7a038dd15ca7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
