Hi; I've written a Search API in front of my SolrCloud. When a user sends a query it goes to my Search API (that uses Solrj). Query is validated, fixed and filled with some default parameters that a user can not change and after that query goes to the SolrCloud.
It allows me to expose my index via JAX-RS, JAX-WS and OpenSearch format (Atom, RSS, XHTML). Beside the security issues I allow a user to write queries something like that within my API: *title: title to search* *url: url to search* It is not a hard task to implement something like that. There is just one thing to consider: API should run fast otherwise it causes a bottleneck in front of the SolrCloud. On the other hand there are some security layers that is provided with hardware at my architecture. Thanks; Furkan KAMACI 2014/1/23 <lia...@gmail.com> > I've been thinking of using nodejs as a thin layer between the client and > solr servers. it seems pretty handy for adding features like throttling, > load balancing and basic authentications. -lianyi > > On Wed, Jan 22, 2014 at 7:36 PM, Alexandre Rafalovitch <arafa...@gmail.com > > > wrote: > > > I thought about Go, but that does not give the advantages of spanning > > client and server like Dart and Node/Javascript. Which is why Dart > > felt a bit more interesting, especially with tree-shaking of unused > > code. > > But then, neither language has enough adoption to be an answer to my > > original question right now (existing middleware for new people to > > pick). So, that's a more theoretical part of the discussion. > > Regards, > > Alex. > > Personal website: http://www.outerthoughts.com/ > > LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > > - Time is the quality of nature that keeps events from happening all > > at once. Lately, it doesn't seem to be working. (Anonymous - via GTD > > book) > > On Thu, Jan 23, 2014 at 4:29 AM, Jorge Luis Betancourt González > > <jlbetanco...@uci.cu> wrote: > >> I would love to see some proxy-like application implemented in go > (partly for my desire of having time to check out go). > >> > >> ----- Original Message ----- > >> From: "Shawn Heisey" <s...@elyograg.org> > >> To: solr-user@lucene.apache.org > >> Sent: Wednesday, January 22, 2014 10:38:34 AM > >> Subject: Re: Solr middle-ware? > >> > >> On 1/22/2014 12:25 AM, Raymond Wiker wrote: > >>> Speaking for myself, I avoid using "client apis" like SolrNet, SolrJ > and > >>> FAST DSAPI for the simple reason that I feel that the abstractions they > >>> offer are so thin that I may just as well talk directly to the HTTP > >>> interface. Doing that also lets me build web applications that maintain > >>> their own state, which makes for more responsive and more robust > >>> applications (although I'm sure there will be differing opinions on > this). > >> > >> If you have the programming skill, this is absolutely a great way to go. > >> It does require a lot of knowledge and expertise, though. > >> > >> If you want to hammer out a quick program and be reasonably sure it's > >> right, a client API handles a lot of the hard stuff for you. When > >> something changes in a new version of Solr that breaks a client API, > >> just upgrading the client API is often enough to make the same code work > >> again. > >> > >> I love SolrJ. It's part of Solr itself, used internally for SolrCloud, > >> and probably replication too. It's thoroughly tested with the Solr test > >> suite, and if used correctly, it's pretty much guaranteed to be > >> compatible with the same version of Solr. In most cases, it will work > >> with other versions too. > >> > >> Thanks, > >> Shawn > >> > >> > ________________________________________________________________________________________________ > >> III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero > del 2014. Ver www.uci.cu >
