Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id F26A3200CDD for ; Mon, 7 Aug 2017 15:36:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EDC96165531; Mon, 7 Aug 2017 13:36:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3CF2F165530 for ; Mon, 7 Aug 2017 15:36:46 +0200 (CEST) Received: (qmail 26412 invoked by uid 500); 7 Aug 2017 13:36:44 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 26395 invoked by uid 99); 7 Aug 2017 13:36:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Aug 2017 13:36:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 79D6318070B for ; Mon, 7 Aug 2017 13:36:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.58 X-Spam-Level: * X-Spam-Status: No, score=1.58 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, KAM_COUK=1.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=flax-co-uk.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id YTkuCxZjOOw5 for ; Mon, 7 Aug 2017 13:36:37 +0000 (UTC) Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 405D45F249 for ; Mon, 7 Aug 2017 13:36:37 +0000 (UTC) Received: by mail-wm0-f43.google.com with SMTP id t201so7338749wmt.0 for ; Mon, 07 Aug 2017 06:36:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flax-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=/OH6l7GAAllLMMauLNSS86S8/y0sdIdm8HxqqSplHNQ=; b=0kBPaQN9AxZIazamf5rtY6bea2KNIVXGxla1rH2LMIK76UrvJMfK6pjLAYHtS3Rv3/ KEbVIykoSveh/x55shOOAMcTX2UBp9Aqp4sFa7dL7QEtpZzcr4r7SHQXwCynRjHwdVaY nojJg6QxUUDmgCspb978LTQ6bk7zBixFNaQOa3VrUCAS6GTW02LM9cmMYKOwjrt19bMJ JqzedpV5tRNZkbw+terdTTwA8tVvCT9P75ws3QtfyVaKYiVv9fls4L2VTknavg2SgxEk dtJpgxWrdWGtVFu37ngYCpY6l41jqK+NZ2XystDwaUethmP15aGnqevqJt6IhmuRK6ni OHYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=/OH6l7GAAllLMMauLNSS86S8/y0sdIdm8HxqqSplHNQ=; b=ItmRgjAfKz0V6Vz7rrNqF/lDrF0OUrClQo6Pb5xncncIA2M5w4TG1G6OMeH02KtY6k WPeTsADvKC/hVL81CVWr5K2IHQW1ImB/UmXHYugpgKIJ9LpmSRN2HljWqLVwquU0E2aI Qd4xNcawdQkyfSliX29dK1pMtbp7PNczmuB0jzakpPuszn0KS8OT5b2CFwezB1BqPqW2 TzkK54P0grfaY7C6jeP9FW7CqwKB7JCUGF4KBDpL87/TmiOF9QU7znOMABMRaW0svCMZ FjXVO1RmNcR83Xcxs59Iur81V8kQhCK6dCGgtQUiEbCzQ0xhugCxsUx8S7AhB3Vj788k pCqA== X-Gm-Message-State: AHYfb5gamkOWKa+KY+rsuTxZz9Msqk1U8Z6x+xsraI3IaqjqXAFf+EWz qjXnpPGPxxgPgnq8U6E= X-Received: by 10.28.43.71 with SMTP id r68mr686170wmr.66.1502112995817; Mon, 07 Aug 2017 06:36:35 -0700 (PDT) Received: from [192.168.1.68] (charliejuggler.plus.com. [80.229.29.33]) by smtp.googlemail.com with ESMTPSA id 134sm5417104wmw.24.2017.08.07.06.36.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Aug 2017 06:36:35 -0700 (PDT) Subject: Re: Architecture: How to commercialise a Solr based application? To: solr-user@lucene.apache.org References: <05435EB7-BCEC-4787-9472-2209A364FA56@gmail.com> From: Charlie Hull Message-ID: Date: Mon, 7 Aug 2017 14:36:34 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <05435EB7-BCEC-4787-9472-2209A364FA56@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit archived-at: Mon, 07 Aug 2017 13:36:47 -0000 Hi Paul, You should be aware you're doing something that has been tried many times before - there are lots of Lucene-based 'packaged' search products out there, from Searchblox to Lucidworks Fusion to Attivio. It's not a small task. You should focus not on the technology (you could build this with pretty much anything) but rather the user need and what you'll do to address it, by building easy-to-use admin UIs, clever ingestion pipelines or whatever. None of your users will care about which language or platform you use, but they'll care about what capabilities they get for their money (and what this gives them over and above Solr). You might start by reading some background texts such as Martin White's excellent Enteprise Search, Doug Turnbull & John Berryman also excellent Relevant Search, Tony Russell-Rose & Tyler Tate's Designing the Search Experience and the book I've just co-authored with Professor Udo Krutschwitz, Searching the Enterprise. Really I'm only scratching the surface here, this is potentially a very big subject! Cheers Charlie On 06/08/2017 13:46, Paul Smith Parker wrote: > Hello, > > I am building a search application based on single core Solr 6.6 server, with an Angular frontend. > Between the frontend and the Solr server I am thinking of using a Java backend (this to avoid exposing Solr end points directly to the frontend). > > I would like to package all those components and commercialise the final product. > > Do you have any advice on what technology I should use to build this final product? > > I would do the installation at customer’s premise, including data import, maintenance and support. > > Ideally, I would like the customer to access only the frontend and never access the Solr configuration files nor call the Solr endpoints directly. > > Initially I thought of delivering a Linux based VM, but that seems a bit too heavy. > Another idea is to create a docker container with all components. > > In any case I need some kind of licensing mechanism that prevents the customer from installing/running an arbitrary number of instances (the commercial model is based on a pay per installation approach). > > I know this is not Solr specific, but I was wondering if you could share your experience on how to commercialise a Solr based application. > > Any help is much appreciated. > > Thank you, > Paul > > > > > --- > This email has been checked for viruses by AVG. > http://www.avg.com > -- Charlie Hull Flax - Open Source Enterprise Search tel/fax: +44 (0)8700 118334 mobile: +44 (0)7767 825828 web: www.flax.co.uk