Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Received-SPF: error (nike.apache.org: local policy)
Date: Sun, 8 Feb 2015 23:51:14 +0000
From: Konstantin Boudnik <cos@apache.org>
To: dev@ignite.incubator.apache.org
Subject: Re: Managed Services -> Service Grid
Message-ID: <20150208235114.GJ4732@boudnik.org>
References: 
 <CA+0=VoVD=cP8dVxwCtzbo6h=FkCD8pc_YgHNwfvAbvpmVRXNWQ@mail.gmail.com>
 <CAGcMBHgPuuMFG3MpSjRBbi3K0=4XpMVKjAfRmk2HA34Gr1zP9Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: 
 <CAGcMBHgPuuMFG3MpSjRBbi3K0=4XpMVKjAfRmk2HA34Gr1zP9Q@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

Sounds good. I guess it'd be quite a fun to try running containers/uni-kernels
with pre-packaged services like that ;)

On Thu, Feb 05, 2015 at 02:02PM, Yakov Zhdanov wrote:
> How about IgniteService? Looks consistent with IgniteCompute, IgniteCache,
> etc we have.
> 
> --
> Yakov Zhdanov, Director R&D
> *GridGain Systems*
> www.gridgain.com
> 
> 2015-02-05 5:36 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org>:
> 
> > Hi,
> >
> > I would like to propose rebranding our Managed Services functionality into
> > Service Grid. I have asked around and "managed services" sounds confusing
> > and does not resonate with developers. Service Grid on the other hand is
> > more consistent with Data Grid and Compute Grid components provided by
> > Ignite.
> >
> > Service Grid provides such features as cluster-singleton,
> > per-node-singleton, SLA-based deployments, guaranteed continuous
> > availability of a service in case of failures, etc.
> >
> > Let me know your thoughts on the naming.
> >
> > D.
> >