You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Alexey Kuznetsov <ak...@gridgain.com> on 2015/06/29 09:33:19 UTC
Web config download
Igniters,
We are working on Ignite Web Config (ignite-843) and very close to first
version of it.
As usual everything could be launched from sources, but for usability issue
I'm thinking
about a kind of installer for web config.
In web config we are using: nodejs, mongodb, angular.
Does any one has experience of packaging web applications for later
deployment?
Any ideas are very appreciated.
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Web config download
Posted by Sergey Evdokimov <se...@gridgain.com>.
We don't have enough users to heavy load. Heavy load cannot be a problem
for WebConfig.
On Tue, Jun 30, 2015 at 6:49 PM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> Just my thoughts.
>
> We could implement some abstraction layer for backend persistence.
> And in case of user download we will package with H2 as default storage.
>
> But in case of heavy load any other db could be used, but will require
> manual installation and configuration.
>
> We are expecting million requests per second?
> I think H2 will be enough? What do you think?
>
>
> On Tue, Jun 30, 2015 at 10:27 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
> >
> wrote:
>
> > And what do you suggest we use as persistence on the backend? Currently
> we
> > use Mongo.
> >
> > D.
> >
> > On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <
> sergi.vladykin@gmail.com>
> > wrote:
> >
> > > And there is nothing to do from scratch here, all the html and client
> > side
> > > js are the same, just switch backend.
> > >
> > > Sergi
> > >
> > > 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <se...@gmail.com>:
> > >
> > > > I think at current stage if it takes two days to switch things, then
> it
> > > > makes sense. We will not be able to do it later.
> > > >
> > > > We will need to have a separate distribution for each supported
> > platform.
> > > > And test each individually.
> > > >
> > > > Sergi
> > > >
> > > > 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <ds...@apache.org>:
> > > >
> > > >> Guys,
> > > >>
> > > >> I would like to avoid "let's drop everything and redo from scratch"
> > > >> discussions. I don't think they will productively get us there.
> > > >>
> > > >> The stack was chosen because it required zero code or integration on
> > the
> > > >> server side and was easiest to implement. Let's try to answer how to
> > > make
> > > >> it downloadable in the easiest way.
> > > >>
> > > >> D.
> > > >>
> > > >> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
> > > sergi.vladykin@gmail.com
> > > >> >
> > > >> wrote:
> > > >>
> > > >> > Guys,
> > > >> >
> > > >> > To be honest I don't know why we choose this stack which is
> > completely
> > > >> > alien to java when our main product is java based. I'm sure in the
> > > >> future
> > > >> > we will need better level of integration between them not only for
> > > >> Ignite
> > > >> > SQL schema import.
> > > >> >
> > > >> > Jetty it is a battle tested server, I think we can go ahead with
> it.
> > > >> > Moreover if we will not be satisfied we can replace it with
> > something
> > > >> else
> > > >> > easily, while I don't know how we will replace node.js in a case.
> > > >> >
> > > >> > As for JSON Alexey, please describe what kind of operations we do
> > with
> > > >> JSON
> > > >> > data and why we can't store it just as a String and be as DB
> neutral
> > > as
> > > >> > possible?
> > > >> >
> > > >> > Sergi
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <
> akuznetsov@gridgain.com
> > >:
> > > >> >
> > > >> > > Sergey,
> > > >> > >
> > > >> > > 1. How many connections Jetty + H2 could handle?
> > > >> > > Do you have any experience?
> > > >> > >
> > > >> > > 2. What is the best way to store JSON into db and later read
> JSON
> > > from
> > > >> > db?
> > > >> > >
> > > >> > > 3. Persistence feature could not be separated, because
> > > >> CacheTypeMetadata
> > > >> > is
> > > >> > > a part of CacheConfiguration.
> > > >> > >
> > > >> > > Dmitriy,
> > > >> > > What do you think about dropping nodejs and mongoDB in favor of
> > > >> > jetty+h2 ?
> > > >> > >
> > > >> > > One more benefit of using java that we could reuse code from
> > Ignite
> > > >> > Schema
> > > >> > > Import
> > > >> > > for connecting to database (using JDBC) and reuse code that
> > > generates
> > > >> > XML
> > > >> > > and POJO classes.
> > > >> > >
> > > >> > > Also we could build and package Web Config with Maven I think.
> > > >> > >
> > > >> > > Actually we do not have much code at server side. So we could
> > switch
> > > >> in a
> > > >> > > couple of days I think.
> > > >> > >
> > > >> > > Thoughts?
> > > >> > >
> > > >> > >
> > > >> > > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> > > >> > sevdokimov@gridgain.com
> > > >> > > >
> > > >> > > wrote:
> > > >> > >
> > > >> > > > I doubt that people will install docker to run WebConfig.
> > > >> > > >
> > > >> > > > If we expect running WebConfig on user machine node.js +
> mongoDB
> > > is
> > > >> a
> > > >> > bad
> > > >> > > > choose. Most of our users are java developers, the plain way
> is
> > to
> > > >> use
> > > >> > > > Jetty + H2 and pack whole WebConfig to single jar. User will
> be
> > > >> start
> > > >> > it
> > > >> > > > using "java -jar webConfig.jar" without unnecessary actions.
> > > >> > > >
> > > >> > > > As I understand, only Persistence feature requires
> installation
> > > >> > WebConfig
> > > >> > > > on local machine, my be you should create separated project
> > > >> > > > PersistenceGenerator that will use Jetty+H2 and will be packed
> > to
> > > >> > single
> > > >> > > > jar.
> > > >> > > >
> > > >> > > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> > > >> > > akuznetsov@gridgain.com
> > > >> > > > >
> > > >> > > > wrote:
> > > >> > > >
> > > >> > > > > What about docker image?
> > > >> > > > > We will create docker image with installed nodejs, mongo and
> > > >> Ignite
> > > >> > Web
> > > >> > > > > Config.
> > > >> > > > > Will this solve this problem?
> > > >> > > > >
> > > >> > > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > > >> > > > dsetrakyan@apache.org>
> > > >> > > > > wrote:
> > > >> > > > >
> > > >> > > > > > From my standpoint, I would like the web-config-download
> to
> > > come
> > > >> > as a
> > > >> > > > zip
> > > >> > > > > > file without any extra installation steps if possible.
> > > >> > > > > >
> > > >> > > > > > Ideally, a user should be able to just download it, unzip
> > it,
> > > >> and
> > > >> > > start
> > > >> > > > > > using it.
> > > >> > > > > >
> > > >> > > > > > D.
> > > >> > > > > >
> > > >> > > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > > >> > > > > > akuznetsov@gridgain.com>
> > > >> > > > > > wrote:
> > > >> > > > > >
> > > >> > > > > > > Igniters,
> > > >> > > > > > >
> > > >> > > > > > > We are working on Ignite Web Config (ignite-843) and
> very
> > > >> close
> > > >> > to
> > > >> > > > > first
> > > >> > > > > > > version of it.
> > > >> > > > > > > As usual everything could be launched from sources, but
> > for
> > > >> > > usability
> > > >> > > > > > issue
> > > >> > > > > > > I'm thinking
> > > >> > > > > > > about a kind of installer for web config.
> > > >> > > > > > >
> > > >> > > > > > > In web config we are using: nodejs, mongodb, angular.
> > > >> > > > > > >
> > > >> > > > > > > Does any one has experience of packaging web
> applications
> > > for
> > > >> > later
> > > >> > > > > > > deployment?
> > > >> > > > > > >
> > > >> > > > > > > Any ideas are very appreciated.
> > > >> > > > > > >
> > > >> > > > > > > --
> > > >> > > > > > > Alexey Kuznetsov
> > > >> > > > > > > GridGain Systems
> > > >> > > > > > > www.gridgain.com
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > --
> > > >> > > > > Alexey Kuznetsov
> > > >> > > > > GridGain Systems
> > > >> > > > > www.gridgain.com
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Alexey Kuznetsov
> > > >> > > GridGain Systems
> > > >> > > www.gridgain.com
> > > >> > >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: Web config download
Posted by Dmitriy Setrakyan <ds...@apache.org>.
My comments are below...
On Tue, Jun 30, 2015 at 7:01 PM, Andrey Novikov <no...@gmail.com> wrote:
> If we try to switch from
> node.js:
> Need implements authorization and authentication from scratch.
>
I was thinking a table in H2: userId | username | pswdhash
> Need implement integration with less, jade.
>
Aren't these the tools to generate HTML and CSS? What would need to be done
differently here?
> Need rewrite rest logic.
> mongo:
> We use mongo specific query by json. Need transform this to relation model.
>
No need to use relational mode. I was thinking a table in H2: userId |
jsonString . Then use JSonPath to search through the string in code.1
> We store user session and account in mongo using node.js module. Need
> write from scratch such integration.
>
Can you check if there is something equivalent in Java?
>
> Actually I don’t think that this will be so easy. I don’t have experience
> with writing such functionality under java.
> We could switch in one or two week I think.
>
>
> > 01 Jul 2015, в 06:37, Sergi Vladykin <se...@gmail.com>
> написал(а):
> >
> > Agree with Alexey about abstracting database layer. Everything else must
> > work as it does now.
> >
> > Sergi
> >
> > 2015-06-30 9:20 GMT-07:00 Alexey Kuznetsov <ak...@gridgain.com>:
> >
> >> I think we could continue with AngularJS and Bootstrap for frontend.
> >>
> >> On Tue, Jun 30, 2015 at 11:05 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org
> >>>
> >> wrote:
> >>
> >>> How about the rest of the stack?
> >>>
> >>> On Tue, Jun 30, 2015 at 9:03 AM, Alexey Kuznetsov <
> >> akuznetsov@gridgain.com
> >>>>
> >>> wrote:
> >>>
> >>>> If we switch for jetty - we do NOT need node.js.
> >>>> If we switch to H2 - we do NOT need MongoDB.
> >>>>
> >>>> On Tue, Jun 30, 2015 at 10:52 PM, Dmitriy Setrakyan <
> >>> dsetrakyan@apache.org
> >>>>>
> >>>> wrote:
> >>>>
> >>>>> We are still going to need node.js, right?
> >>>>>
> >>>>> On Tue, Jun 30, 2015 at 8:49 AM, Alexey Kuznetsov <
> >>>> akuznetsov@gridgain.com
> >>>>>>
> >>>>> wrote:
> >>>>>
> >>>>>> Just my thoughts.
> >>>>>>
> >>>>>> We could implement some abstraction layer for backend persistence.
> >>>>>> And in case of user download we will package with H2 as default
> >>>> storage.
> >>>>>>
> >>>>>> But in case of heavy load any other db could be used, but will
> >>> require
> >>>>>> manual installation and configuration.
> >>>>>>
> >>>>>> We are expecting million requests per second?
> >>>>>> I think H2 will be enough? What do you think?
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Jun 30, 2015 at 10:27 PM, Dmitriy Setrakyan <
> >>>>> dsetrakyan@apache.org
> >>>>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> And what do you suggest we use as persistence on the backend?
> >>>> Currently
> >>>>>> we
> >>>>>>> use Mongo.
> >>>>>>>
> >>>>>>> D.
> >>>>>>>
> >>>>>>> On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <
> >>>>>> sergi.vladykin@gmail.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> And there is nothing to do from scratch here, all the html and
> >>>> client
> >>>>>>> side
> >>>>>>>> js are the same, just switch backend.
> >>>>>>>>
> >>>>>>>> Sergi
> >>>>>>>>
> >>>>>>>> 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <
> >>> sergi.vladykin@gmail.com
> >>>>> :
> >>>>>>>>
> >>>>>>>>> I think at current stage if it takes two days to switch
> >> things,
> >>>>> then
> >>>>>> it
> >>>>>>>>> makes sense. We will not be able to do it later.
> >>>>>>>>>
> >>>>>>>>> We will need to have a separate distribution for each
> >> supported
> >>>>>>> platform.
> >>>>>>>>> And test each individually.
> >>>>>>>>>
> >>>>>>>>> Sergi
> >>>>>>>>>
> >>>>>>>>> 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <
> >>>> dsetrakyan@apache.org
> >>>>>> :
> >>>>>>>>>
> >>>>>>>>>> Guys,
> >>>>>>>>>>
> >>>>>>>>>> I would like to avoid "let's drop everything and redo from
> >>>>> scratch"
> >>>>>>>>>> discussions. I don't think they will productively get us
> >>> there.
> >>>>>>>>>>
> >>>>>>>>>> The stack was chosen because it required zero code or
> >>>> integration
> >>>>> on
> >>>>>>> the
> >>>>>>>>>> server side and was easiest to implement. Let's try to
> >> answer
> >>>> how
> >>>>> to
> >>>>>>>> make
> >>>>>>>>>> it downloadable in the easiest way.
> >>>>>>>>>>
> >>>>>>>>>> D.
> >>>>>>>>>>
> >>>>>>>>>> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
> >>>>>>>> sergi.vladykin@gmail.com
> >>>>>>>>>>>
> >>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Guys,
> >>>>>>>>>>>
> >>>>>>>>>>> To be honest I don't know why we choose this stack which
> >> is
> >>>>>>> completely
> >>>>>>>>>>> alien to java when our main product is java based. I'm
> >> sure
> >>> in
> >>>>> the
> >>>>>>>>>> future
> >>>>>>>>>>> we will need better level of integration between them not
> >>> only
> >>>>> for
> >>>>>>>>>> Ignite
> >>>>>>>>>>> SQL schema import.
> >>>>>>>>>>>
> >>>>>>>>>>> Jetty it is a battle tested server, I think we can go
> >> ahead
> >>>> with
> >>>>>> it.
> >>>>>>>>>>> Moreover if we will not be satisfied we can replace it
> >> with
> >>>>>>> something
> >>>>>>>>>> else
> >>>>>>>>>>> easily, while I don't know how we will replace node.js in
> >> a
> >>>>> case.
> >>>>>>>>>>>
> >>>>>>>>>>> As for JSON Alexey, please describe what kind of
> >> operations
> >>> we
> >>>>> do
> >>>>>>> with
> >>>>>>>>>> JSON
> >>>>>>>>>>> data and why we can't store it just as a String and be as
> >> DB
> >>>>>> neutral
> >>>>>>>> as
> >>>>>>>>>>> possible?
> >>>>>>>>>>>
> >>>>>>>>>>> Sergi
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <
> >>>>>> akuznetsov@gridgain.com
> >>>>>>>> :
> >>>>>>>>>>>
> >>>>>>>>>>>> Sergey,
> >>>>>>>>>>>>
> >>>>>>>>>>>> 1. How many connections Jetty + H2 could handle?
> >>>>>>>>>>>> Do you have any experience?
> >>>>>>>>>>>>
> >>>>>>>>>>>> 2. What is the best way to store JSON into db and later
> >>> read
> >>>>>> JSON
> >>>>>>>> from
> >>>>>>>>>>> db?
> >>>>>>>>>>>>
> >>>>>>>>>>>> 3. Persistence feature could not be separated, because
> >>>>>>>>>> CacheTypeMetadata
> >>>>>>>>>>> is
> >>>>>>>>>>>> a part of CacheConfiguration.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Dmitriy,
> >>>>>>>>>>>> What do you think about dropping nodejs and mongoDB in
> >>>> favor
> >>>>> of
> >>>>>>>>>>> jetty+h2 ?
> >>>>>>>>>>>>
> >>>>>>>>>>>> One more benefit of using java that we could reuse code
> >>> from
> >>>>>>> Ignite
> >>>>>>>>>>> Schema
> >>>>>>>>>>>> Import
> >>>>>>>>>>>> for connecting to database (using JDBC) and reuse code
> >>> that
> >>>>>>>> generates
> >>>>>>>>>>> XML
> >>>>>>>>>>>> and POJO classes.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Also we could build and package Web Config with Maven I
> >>>> think.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Actually we do not have much code at server side. So we
> >>>> could
> >>>>>>> switch
> >>>>>>>>>> in a
> >>>>>>>>>>>> couple of days I think.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thoughts?
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> >>>>>>>>>>> sevdokimov@gridgain.com
> >>>>>>>>>>>>>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> I doubt that people will install docker to run
> >>> WebConfig.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> If we expect running WebConfig on user machine
> >> node.js +
> >>>>>> mongoDB
> >>>>>>>> is
> >>>>>>>>>> a
> >>>>>>>>>>> bad
> >>>>>>>>>>>>> choose. Most of our users are java developers, the
> >> plain
> >>>> way
> >>>>>> is
> >>>>>>> to
> >>>>>>>>>> use
> >>>>>>>>>>>>> Jetty + H2 and pack whole WebConfig to single jar.
> >> User
> >>>> will
> >>>>>> be
> >>>>>>>>>> start
> >>>>>>>>>>> it
> >>>>>>>>>>>>> using "java -jar webConfig.jar" without unnecessary
> >>>> actions.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> As I understand, only Persistence feature requires
> >>>>>> installation
> >>>>>>>>>>> WebConfig
> >>>>>>>>>>>>> on local machine, my be you should create separated
> >>>> project
> >>>>>>>>>>>>> PersistenceGenerator that will use Jetty+H2 and will
> >> be
> >>>>> packed
> >>>>>>> to
> >>>>>>>>>>> single
> >>>>>>>>>>>>> jar.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> >>>>>>>>>>>> akuznetsov@gridgain.com
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> What about docker image?
> >>>>>>>>>>>>>> We will create docker image with installed nodejs,
> >>> mongo
> >>>>> and
> >>>>>>>>>> Ignite
> >>>>>>>>>>> Web
> >>>>>>>>>>>>>> Config.
> >>>>>>>>>>>>>> Will this solve this problem?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> >>>>>>>>>>>>> dsetrakyan@apache.org>
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> From my standpoint, I would like the
> >>>> web-config-download
> >>>>>> to
> >>>>>>>> come
> >>>>>>>>>>> as a
> >>>>>>>>>>>>> zip
> >>>>>>>>>>>>>>> file without any extra installation steps if
> >>> possible.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Ideally, a user should be able to just download
> >> it,
> >>>>> unzip
> >>>>>>> it,
> >>>>>>>>>> and
> >>>>>>>>>>>> start
> >>>>>>>>>>>>>>> using it.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> D.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Mon, Jun 29, 2015 at 12:33 AM, Alexey
> >> Kuznetsov <
> >>>>>>>>>>>>>>> akuznetsov@gridgain.com>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Igniters,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> We are working on Ignite Web Config (ignite-843)
> >>> and
> >>>>>> very
> >>>>>>>>>> close
> >>>>>>>>>>> to
> >>>>>>>>>>>>>> first
> >>>>>>>>>>>>>>>> version of it.
> >>>>>>>>>>>>>>>> As usual everything could be launched from
> >>> sources,
> >>>>> but
> >>>>>>> for
> >>>>>>>>>>>> usability
> >>>>>>>>>>>>>>> issue
> >>>>>>>>>>>>>>>> I'm thinking
> >>>>>>>>>>>>>>>> about a kind of installer for web config.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> In web config we are using: nodejs, mongodb,
> >>>> angular.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Does any one has experience of packaging web
> >>>>>> applications
> >>>>>>>> for
> >>>>>>>>>>> later
> >>>>>>>>>>>>>>>> deployment?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Any ideas are very appreciated.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>> Alexey Kuznetsov
> >>>>>>>>>>>>>>>> GridGain Systems
> >>>>>>>>>>>>>>>> www.gridgain.com
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Alexey Kuznetsov
> >>>>>>>>>>>>>> GridGain Systems
> >>>>>>>>>>>>>> www.gridgain.com
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Alexey Kuznetsov
> >>>>>>>>>>>> GridGain Systems
> >>>>>>>>>>>> www.gridgain.com
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Alexey Kuznetsov
> >>>>>> GridGain Systems
> >>>>>> www.gridgain.com
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Alexey Kuznetsov
> >>>> GridGain Systems
> >>>> www.gridgain.com
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >> Alexey Kuznetsov
> >> GridGain Systems
> >> www.gridgain.com
> >>
>
>
Re: Web config download
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
>> Need implement integration with less, jade.
For now JADE could be used from command line and generate html pages.
Later we could replace JADE with native java template engine.
Web Storm/Idea could generate css from less on the fly, no integration
needed.
>>We use mongo specific query by json. Need transform this to relation
model.
We use VERY simple model for now.
All we need is ID, USER_ID, SPACE_ID, JSON (as Text/blob)
The most hard thing so far is authorization and authentication.
But I hope that it is already solved and we could find a solution in Google.
On Wed, Jul 1, 2015 at 9:01 AM, Andrey Novikov <no...@gmail.com> wrote:
> If we try to switch from
> node.js:
> Need implements authorization and authentication from scratch.
> Need implement integration with less, jade.
> Need rewrite rest logic.
> mongo:
> We use mongo specific query by json. Need transform this to relation model.
> We store user session and account in mongo using node.js module. Need
> write from scratch such integration.
>
> Actually I don’t think that this will be so easy. I don’t have experience
> with writing such functionality under java.
> We could switch in one or two week I think.
>
>
> > 01 Jul 2015, в 06:37, Sergi Vladykin <se...@gmail.com>
> написал(а):
> >
> > Agree with Alexey about abstracting database layer. Everything else must
> > work as it does now.
> >
> > Sergi
> >
> > 2015-06-30 9:20 GMT-07:00 Alexey Kuznetsov <ak...@gridgain.com>:
> >
> >> I think we could continue with AngularJS and Bootstrap for frontend.
> >>
> >> On Tue, Jun 30, 2015 at 11:05 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org
> >>>
> >> wrote:
> >>
> >>> How about the rest of the stack?
> >>>
> >>> On Tue, Jun 30, 2015 at 9:03 AM, Alexey Kuznetsov <
> >> akuznetsov@gridgain.com
> >>>>
> >>> wrote:
> >>>
> >>>> If we switch for jetty - we do NOT need node.js.
> >>>> If we switch to H2 - we do NOT need MongoDB.
> >>>>
> >>>> On Tue, Jun 30, 2015 at 10:52 PM, Dmitriy Setrakyan <
> >>> dsetrakyan@apache.org
> >>>>>
> >>>> wrote:
> >>>>
> >>>>> We are still going to need node.js, right?
> >>>>>
> >>>>> On Tue, Jun 30, 2015 at 8:49 AM, Alexey Kuznetsov <
> >>>> akuznetsov@gridgain.com
> >>>>>>
> >>>>> wrote:
> >>>>>
> >>>>>> Just my thoughts.
> >>>>>>
> >>>>>> We could implement some abstraction layer for backend persistence.
> >>>>>> And in case of user download we will package with H2 as default
> >>>> storage.
> >>>>>>
> >>>>>> But in case of heavy load any other db could be used, but will
> >>> require
> >>>>>> manual installation and configuration.
> >>>>>>
> >>>>>> We are expecting million requests per second?
> >>>>>> I think H2 will be enough? What do you think?
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Jun 30, 2015 at 10:27 PM, Dmitriy Setrakyan <
> >>>>> dsetrakyan@apache.org
> >>>>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> And what do you suggest we use as persistence on the backend?
> >>>> Currently
> >>>>>> we
> >>>>>>> use Mongo.
> >>>>>>>
> >>>>>>> D.
> >>>>>>>
> >>>>>>> On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <
> >>>>>> sergi.vladykin@gmail.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> And there is nothing to do from scratch here, all the html and
> >>>> client
> >>>>>>> side
> >>>>>>>> js are the same, just switch backend.
> >>>>>>>>
> >>>>>>>> Sergi
> >>>>>>>>
> >>>>>>>> 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <
> >>> sergi.vladykin@gmail.com
> >>>>> :
> >>>>>>>>
> >>>>>>>>> I think at current stage if it takes two days to switch
> >> things,
> >>>>> then
> >>>>>> it
> >>>>>>>>> makes sense. We will not be able to do it later.
> >>>>>>>>>
> >>>>>>>>> We will need to have a separate distribution for each
> >> supported
> >>>>>>> platform.
> >>>>>>>>> And test each individually.
> >>>>>>>>>
> >>>>>>>>> Sergi
> >>>>>>>>>
> >>>>>>>>> 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <
> >>>> dsetrakyan@apache.org
> >>>>>> :
> >>>>>>>>>
> >>>>>>>>>> Guys,
> >>>>>>>>>>
> >>>>>>>>>> I would like to avoid "let's drop everything and redo from
> >>>>> scratch"
> >>>>>>>>>> discussions. I don't think they will productively get us
> >>> there.
> >>>>>>>>>>
> >>>>>>>>>> The stack was chosen because it required zero code or
> >>>> integration
> >>>>> on
> >>>>>>> the
> >>>>>>>>>> server side and was easiest to implement. Let's try to
> >> answer
> >>>> how
> >>>>> to
> >>>>>>>> make
> >>>>>>>>>> it downloadable in the easiest way.
> >>>>>>>>>>
> >>>>>>>>>> D.
> >>>>>>>>>>
> >>>>>>>>>> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
> >>>>>>>> sergi.vladykin@gmail.com
> >>>>>>>>>>>
> >>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Guys,
> >>>>>>>>>>>
> >>>>>>>>>>> To be honest I don't know why we choose this stack which
> >> is
> >>>>>>> completely
> >>>>>>>>>>> alien to java when our main product is java based. I'm
> >> sure
> >>> in
> >>>>> the
> >>>>>>>>>> future
> >>>>>>>>>>> we will need better level of integration between them not
> >>> only
> >>>>> for
> >>>>>>>>>> Ignite
> >>>>>>>>>>> SQL schema import.
> >>>>>>>>>>>
> >>>>>>>>>>> Jetty it is a battle tested server, I think we can go
> >> ahead
> >>>> with
> >>>>>> it.
> >>>>>>>>>>> Moreover if we will not be satisfied we can replace it
> >> with
> >>>>>>> something
> >>>>>>>>>> else
> >>>>>>>>>>> easily, while I don't know how we will replace node.js in
> >> a
> >>>>> case.
> >>>>>>>>>>>
> >>>>>>>>>>> As for JSON Alexey, please describe what kind of
> >> operations
> >>> we
> >>>>> do
> >>>>>>> with
> >>>>>>>>>> JSON
> >>>>>>>>>>> data and why we can't store it just as a String and be as
> >> DB
> >>>>>> neutral
> >>>>>>>> as
> >>>>>>>>>>> possible?
> >>>>>>>>>>>
> >>>>>>>>>>> Sergi
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <
> >>>>>> akuznetsov@gridgain.com
> >>>>>>>> :
> >>>>>>>>>>>
> >>>>>>>>>>>> Sergey,
> >>>>>>>>>>>>
> >>>>>>>>>>>> 1. How many connections Jetty + H2 could handle?
> >>>>>>>>>>>> Do you have any experience?
> >>>>>>>>>>>>
> >>>>>>>>>>>> 2. What is the best way to store JSON into db and later
> >>> read
> >>>>>> JSON
> >>>>>>>> from
> >>>>>>>>>>> db?
> >>>>>>>>>>>>
> >>>>>>>>>>>> 3. Persistence feature could not be separated, because
> >>>>>>>>>> CacheTypeMetadata
> >>>>>>>>>>> is
> >>>>>>>>>>>> a part of CacheConfiguration.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Dmitriy,
> >>>>>>>>>>>> What do you think about dropping nodejs and mongoDB in
> >>>> favor
> >>>>> of
> >>>>>>>>>>> jetty+h2 ?
> >>>>>>>>>>>>
> >>>>>>>>>>>> One more benefit of using java that we could reuse code
> >>> from
> >>>>>>> Ignite
> >>>>>>>>>>> Schema
> >>>>>>>>>>>> Import
> >>>>>>>>>>>> for connecting to database (using JDBC) and reuse code
> >>> that
> >>>>>>>> generates
> >>>>>>>>>>> XML
> >>>>>>>>>>>> and POJO classes.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Also we could build and package Web Config with Maven I
> >>>> think.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Actually we do not have much code at server side. So we
> >>>> could
> >>>>>>> switch
> >>>>>>>>>> in a
> >>>>>>>>>>>> couple of days I think.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thoughts?
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> >>>>>>>>>>> sevdokimov@gridgain.com
> >>>>>>>>>>>>>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> I doubt that people will install docker to run
> >>> WebConfig.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> If we expect running WebConfig on user machine
> >> node.js +
> >>>>>> mongoDB
> >>>>>>>> is
> >>>>>>>>>> a
> >>>>>>>>>>> bad
> >>>>>>>>>>>>> choose. Most of our users are java developers, the
> >> plain
> >>>> way
> >>>>>> is
> >>>>>>> to
> >>>>>>>>>> use
> >>>>>>>>>>>>> Jetty + H2 and pack whole WebConfig to single jar.
> >> User
> >>>> will
> >>>>>> be
> >>>>>>>>>> start
> >>>>>>>>>>> it
> >>>>>>>>>>>>> using "java -jar webConfig.jar" without unnecessary
> >>>> actions.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> As I understand, only Persistence feature requires
> >>>>>> installation
> >>>>>>>>>>> WebConfig
> >>>>>>>>>>>>> on local machine, my be you should create separated
> >>>> project
> >>>>>>>>>>>>> PersistenceGenerator that will use Jetty+H2 and will
> >> be
> >>>>> packed
> >>>>>>> to
> >>>>>>>>>>> single
> >>>>>>>>>>>>> jar.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> >>>>>>>>>>>> akuznetsov@gridgain.com
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> What about docker image?
> >>>>>>>>>>>>>> We will create docker image with installed nodejs,
> >>> mongo
> >>>>> and
> >>>>>>>>>> Ignite
> >>>>>>>>>>> Web
> >>>>>>>>>>>>>> Config.
> >>>>>>>>>>>>>> Will this solve this problem?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> >>>>>>>>>>>>> dsetrakyan@apache.org>
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> From my standpoint, I would like the
> >>>> web-config-download
> >>>>>> to
> >>>>>>>> come
> >>>>>>>>>>> as a
> >>>>>>>>>>>>> zip
> >>>>>>>>>>>>>>> file without any extra installation steps if
> >>> possible.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Ideally, a user should be able to just download
> >> it,
> >>>>> unzip
> >>>>>>> it,
> >>>>>>>>>> and
> >>>>>>>>>>>> start
> >>>>>>>>>>>>>>> using it.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> D.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Mon, Jun 29, 2015 at 12:33 AM, Alexey
> >> Kuznetsov <
> >>>>>>>>>>>>>>> akuznetsov@gridgain.com>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Igniters,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> We are working on Ignite Web Config (ignite-843)
> >>> and
> >>>>>> very
> >>>>>>>>>> close
> >>>>>>>>>>> to
> >>>>>>>>>>>>>> first
> >>>>>>>>>>>>>>>> version of it.
> >>>>>>>>>>>>>>>> As usual everything could be launched from
> >>> sources,
> >>>>> but
> >>>>>>> for
> >>>>>>>>>>>> usability
> >>>>>>>>>>>>>>> issue
> >>>>>>>>>>>>>>>> I'm thinking
> >>>>>>>>>>>>>>>> about a kind of installer for web config.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> In web config we are using: nodejs, mongodb,
> >>>> angular.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Does any one has experience of packaging web
> >>>>>> applications
> >>>>>>>> for
> >>>>>>>>>>> later
> >>>>>>>>>>>>>>>> deployment?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Any ideas are very appreciated.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>> Alexey Kuznetsov
> >>>>>>>>>>>>>>>> GridGain Systems
> >>>>>>>>>>>>>>>> www.gridgain.com
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Alexey Kuznetsov
> >>>>>>>>>>>>>> GridGain Systems
> >>>>>>>>>>>>>> www.gridgain.com
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Alexey Kuznetsov
> >>>>>>>>>>>> GridGain Systems
> >>>>>>>>>>>> www.gridgain.com
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Alexey Kuznetsov
> >>>>>> GridGain Systems
> >>>>>> www.gridgain.com
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Alexey Kuznetsov
> >>>> GridGain Systems
> >>>> www.gridgain.com
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >> Alexey Kuznetsov
> >> GridGain Systems
> >> www.gridgain.com
> >>
>
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Web config download
Posted by Andrey Novikov <no...@gmail.com>.
If we try to switch from
node.js:
Need implements authorization and authentication from scratch.
Need implement integration with less, jade.
Need rewrite rest logic.
mongo:
We use mongo specific query by json. Need transform this to relation model.
We store user session and account in mongo using node.js module. Need write from scratch such integration.
Actually I don’t think that this will be so easy. I don’t have experience with writing such functionality under java.
We could switch in one or two week I think.
> 01 Jul 2015, в 06:37, Sergi Vladykin <se...@gmail.com> написал(а):
>
> Agree with Alexey about abstracting database layer. Everything else must
> work as it does now.
>
> Sergi
>
> 2015-06-30 9:20 GMT-07:00 Alexey Kuznetsov <ak...@gridgain.com>:
>
>> I think we could continue with AngularJS and Bootstrap for frontend.
>>
>> On Tue, Jun 30, 2015 at 11:05 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
>>>
>> wrote:
>>
>>> How about the rest of the stack?
>>>
>>> On Tue, Jun 30, 2015 at 9:03 AM, Alexey Kuznetsov <
>> akuznetsov@gridgain.com
>>>>
>>> wrote:
>>>
>>>> If we switch for jetty - we do NOT need node.js.
>>>> If we switch to H2 - we do NOT need MongoDB.
>>>>
>>>> On Tue, Jun 30, 2015 at 10:52 PM, Dmitriy Setrakyan <
>>> dsetrakyan@apache.org
>>>>>
>>>> wrote:
>>>>
>>>>> We are still going to need node.js, right?
>>>>>
>>>>> On Tue, Jun 30, 2015 at 8:49 AM, Alexey Kuznetsov <
>>>> akuznetsov@gridgain.com
>>>>>>
>>>>> wrote:
>>>>>
>>>>>> Just my thoughts.
>>>>>>
>>>>>> We could implement some abstraction layer for backend persistence.
>>>>>> And in case of user download we will package with H2 as default
>>>> storage.
>>>>>>
>>>>>> But in case of heavy load any other db could be used, but will
>>> require
>>>>>> manual installation and configuration.
>>>>>>
>>>>>> We are expecting million requests per second?
>>>>>> I think H2 will be enough? What do you think?
>>>>>>
>>>>>>
>>>>>> On Tue, Jun 30, 2015 at 10:27 PM, Dmitriy Setrakyan <
>>>>> dsetrakyan@apache.org
>>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>> And what do you suggest we use as persistence on the backend?
>>>> Currently
>>>>>> we
>>>>>>> use Mongo.
>>>>>>>
>>>>>>> D.
>>>>>>>
>>>>>>> On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <
>>>>>> sergi.vladykin@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> And there is nothing to do from scratch here, all the html and
>>>> client
>>>>>>> side
>>>>>>>> js are the same, just switch backend.
>>>>>>>>
>>>>>>>> Sergi
>>>>>>>>
>>>>>>>> 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <
>>> sergi.vladykin@gmail.com
>>>>> :
>>>>>>>>
>>>>>>>>> I think at current stage if it takes two days to switch
>> things,
>>>>> then
>>>>>> it
>>>>>>>>> makes sense. We will not be able to do it later.
>>>>>>>>>
>>>>>>>>> We will need to have a separate distribution for each
>> supported
>>>>>>> platform.
>>>>>>>>> And test each individually.
>>>>>>>>>
>>>>>>>>> Sergi
>>>>>>>>>
>>>>>>>>> 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <
>>>> dsetrakyan@apache.org
>>>>>> :
>>>>>>>>>
>>>>>>>>>> Guys,
>>>>>>>>>>
>>>>>>>>>> I would like to avoid "let's drop everything and redo from
>>>>> scratch"
>>>>>>>>>> discussions. I don't think they will productively get us
>>> there.
>>>>>>>>>>
>>>>>>>>>> The stack was chosen because it required zero code or
>>>> integration
>>>>> on
>>>>>>> the
>>>>>>>>>> server side and was easiest to implement. Let's try to
>> answer
>>>> how
>>>>> to
>>>>>>>> make
>>>>>>>>>> it downloadable in the easiest way.
>>>>>>>>>>
>>>>>>>>>> D.
>>>>>>>>>>
>>>>>>>>>> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
>>>>>>>> sergi.vladykin@gmail.com
>>>>>>>>>>>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Guys,
>>>>>>>>>>>
>>>>>>>>>>> To be honest I don't know why we choose this stack which
>> is
>>>>>>> completely
>>>>>>>>>>> alien to java when our main product is java based. I'm
>> sure
>>> in
>>>>> the
>>>>>>>>>> future
>>>>>>>>>>> we will need better level of integration between them not
>>> only
>>>>> for
>>>>>>>>>> Ignite
>>>>>>>>>>> SQL schema import.
>>>>>>>>>>>
>>>>>>>>>>> Jetty it is a battle tested server, I think we can go
>> ahead
>>>> with
>>>>>> it.
>>>>>>>>>>> Moreover if we will not be satisfied we can replace it
>> with
>>>>>>> something
>>>>>>>>>> else
>>>>>>>>>>> easily, while I don't know how we will replace node.js in
>> a
>>>>> case.
>>>>>>>>>>>
>>>>>>>>>>> As for JSON Alexey, please describe what kind of
>> operations
>>> we
>>>>> do
>>>>>>> with
>>>>>>>>>> JSON
>>>>>>>>>>> data and why we can't store it just as a String and be as
>> DB
>>>>>> neutral
>>>>>>>> as
>>>>>>>>>>> possible?
>>>>>>>>>>>
>>>>>>>>>>> Sergi
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <
>>>>>> akuznetsov@gridgain.com
>>>>>>>> :
>>>>>>>>>>>
>>>>>>>>>>>> Sergey,
>>>>>>>>>>>>
>>>>>>>>>>>> 1. How many connections Jetty + H2 could handle?
>>>>>>>>>>>> Do you have any experience?
>>>>>>>>>>>>
>>>>>>>>>>>> 2. What is the best way to store JSON into db and later
>>> read
>>>>>> JSON
>>>>>>>> from
>>>>>>>>>>> db?
>>>>>>>>>>>>
>>>>>>>>>>>> 3. Persistence feature could not be separated, because
>>>>>>>>>> CacheTypeMetadata
>>>>>>>>>>> is
>>>>>>>>>>>> a part of CacheConfiguration.
>>>>>>>>>>>>
>>>>>>>>>>>> Dmitriy,
>>>>>>>>>>>> What do you think about dropping nodejs and mongoDB in
>>>> favor
>>>>> of
>>>>>>>>>>> jetty+h2 ?
>>>>>>>>>>>>
>>>>>>>>>>>> One more benefit of using java that we could reuse code
>>> from
>>>>>>> Ignite
>>>>>>>>>>> Schema
>>>>>>>>>>>> Import
>>>>>>>>>>>> for connecting to database (using JDBC) and reuse code
>>> that
>>>>>>>> generates
>>>>>>>>>>> XML
>>>>>>>>>>>> and POJO classes.
>>>>>>>>>>>>
>>>>>>>>>>>> Also we could build and package Web Config with Maven I
>>>> think.
>>>>>>>>>>>>
>>>>>>>>>>>> Actually we do not have much code at server side. So we
>>>> could
>>>>>>> switch
>>>>>>>>>> in a
>>>>>>>>>>>> couple of days I think.
>>>>>>>>>>>>
>>>>>>>>>>>> Thoughts?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
>>>>>>>>>>> sevdokimov@gridgain.com
>>>>>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I doubt that people will install docker to run
>>> WebConfig.
>>>>>>>>>>>>>
>>>>>>>>>>>>> If we expect running WebConfig on user machine
>> node.js +
>>>>>> mongoDB
>>>>>>>> is
>>>>>>>>>> a
>>>>>>>>>>> bad
>>>>>>>>>>>>> choose. Most of our users are java developers, the
>> plain
>>>> way
>>>>>> is
>>>>>>> to
>>>>>>>>>> use
>>>>>>>>>>>>> Jetty + H2 and pack whole WebConfig to single jar.
>> User
>>>> will
>>>>>> be
>>>>>>>>>> start
>>>>>>>>>>> it
>>>>>>>>>>>>> using "java -jar webConfig.jar" without unnecessary
>>>> actions.
>>>>>>>>>>>>>
>>>>>>>>>>>>> As I understand, only Persistence feature requires
>>>>>> installation
>>>>>>>>>>> WebConfig
>>>>>>>>>>>>> on local machine, my be you should create separated
>>>> project
>>>>>>>>>>>>> PersistenceGenerator that will use Jetty+H2 and will
>> be
>>>>> packed
>>>>>>> to
>>>>>>>>>>> single
>>>>>>>>>>>>> jar.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
>>>>>>>>>>>> akuznetsov@gridgain.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> What about docker image?
>>>>>>>>>>>>>> We will create docker image with installed nodejs,
>>> mongo
>>>>> and
>>>>>>>>>> Ignite
>>>>>>>>>>> Web
>>>>>>>>>>>>>> Config.
>>>>>>>>>>>>>> Will this solve this problem?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
>>>>>>>>>>>>> dsetrakyan@apache.org>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> From my standpoint, I would like the
>>>> web-config-download
>>>>>> to
>>>>>>>> come
>>>>>>>>>>> as a
>>>>>>>>>>>>> zip
>>>>>>>>>>>>>>> file without any extra installation steps if
>>> possible.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Ideally, a user should be able to just download
>> it,
>>>>> unzip
>>>>>>> it,
>>>>>>>>>> and
>>>>>>>>>>>> start
>>>>>>>>>>>>>>> using it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> D.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jun 29, 2015 at 12:33 AM, Alexey
>> Kuznetsov <
>>>>>>>>>>>>>>> akuznetsov@gridgain.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Igniters,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> We are working on Ignite Web Config (ignite-843)
>>> and
>>>>>> very
>>>>>>>>>> close
>>>>>>>>>>> to
>>>>>>>>>>>>>> first
>>>>>>>>>>>>>>>> version of it.
>>>>>>>>>>>>>>>> As usual everything could be launched from
>>> sources,
>>>>> but
>>>>>>> for
>>>>>>>>>>>> usability
>>>>>>>>>>>>>>> issue
>>>>>>>>>>>>>>>> I'm thinking
>>>>>>>>>>>>>>>> about a kind of installer for web config.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> In web config we are using: nodejs, mongodb,
>>>> angular.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Does any one has experience of packaging web
>>>>>> applications
>>>>>>>> for
>>>>>>>>>>> later
>>>>>>>>>>>>>>>> deployment?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Any ideas are very appreciated.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Alexey Kuznetsov
>>>>>>>>>>>>>>>> GridGain Systems
>>>>>>>>>>>>>>>> www.gridgain.com
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Alexey Kuznetsov
>>>>>>>>>>>>>> GridGain Systems
>>>>>>>>>>>>>> www.gridgain.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Alexey Kuznetsov
>>>>>>>>>>>> GridGain Systems
>>>>>>>>>>>> www.gridgain.com
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Alexey Kuznetsov
>>>>>> GridGain Systems
>>>>>> www.gridgain.com
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Alexey Kuznetsov
>>>> GridGain Systems
>>>> www.gridgain.com
>>>>
>>>
>>
>>
>>
>> --
>> Alexey Kuznetsov
>> GridGain Systems
>> www.gridgain.com
>>
Re: Web config download
Posted by Sergi Vladykin <se...@gmail.com>.
Agree with Alexey about abstracting database layer. Everything else must
work as it does now.
Sergi
2015-06-30 9:20 GMT-07:00 Alexey Kuznetsov <ak...@gridgain.com>:
> I think we could continue with AngularJS and Bootstrap for frontend.
>
> On Tue, Jun 30, 2015 at 11:05 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
> >
> wrote:
>
> > How about the rest of the stack?
> >
> > On Tue, Jun 30, 2015 at 9:03 AM, Alexey Kuznetsov <
> akuznetsov@gridgain.com
> > >
> > wrote:
> >
> > > If we switch for jetty - we do NOT need node.js.
> > > If we switch to H2 - we do NOT need MongoDB.
> > >
> > > On Tue, Jun 30, 2015 at 10:52 PM, Dmitriy Setrakyan <
> > dsetrakyan@apache.org
> > > >
> > > wrote:
> > >
> > > > We are still going to need node.js, right?
> > > >
> > > > On Tue, Jun 30, 2015 at 8:49 AM, Alexey Kuznetsov <
> > > akuznetsov@gridgain.com
> > > > >
> > > > wrote:
> > > >
> > > > > Just my thoughts.
> > > > >
> > > > > We could implement some abstraction layer for backend persistence.
> > > > > And in case of user download we will package with H2 as default
> > > storage.
> > > > >
> > > > > But in case of heavy load any other db could be used, but will
> > require
> > > > > manual installation and configuration.
> > > > >
> > > > > We are expecting million requests per second?
> > > > > I think H2 will be enough? What do you think?
> > > > >
> > > > >
> > > > > On Tue, Jun 30, 2015 at 10:27 PM, Dmitriy Setrakyan <
> > > > dsetrakyan@apache.org
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > And what do you suggest we use as persistence on the backend?
> > > Currently
> > > > > we
> > > > > > use Mongo.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <
> > > > > sergi.vladykin@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > And there is nothing to do from scratch here, all the html and
> > > client
> > > > > > side
> > > > > > > js are the same, just switch backend.
> > > > > > >
> > > > > > > Sergi
> > > > > > >
> > > > > > > 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <
> > sergi.vladykin@gmail.com
> > > >:
> > > > > > >
> > > > > > > > I think at current stage if it takes two days to switch
> things,
> > > > then
> > > > > it
> > > > > > > > makes sense. We will not be able to do it later.
> > > > > > > >
> > > > > > > > We will need to have a separate distribution for each
> supported
> > > > > > platform.
> > > > > > > > And test each individually.
> > > > > > > >
> > > > > > > > Sergi
> > > > > > > >
> > > > > > > > 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <
> > > dsetrakyan@apache.org
> > > > >:
> > > > > > > >
> > > > > > > >> Guys,
> > > > > > > >>
> > > > > > > >> I would like to avoid "let's drop everything and redo from
> > > > scratch"
> > > > > > > >> discussions. I don't think they will productively get us
> > there.
> > > > > > > >>
> > > > > > > >> The stack was chosen because it required zero code or
> > > integration
> > > > on
> > > > > > the
> > > > > > > >> server side and was easiest to implement. Let's try to
> answer
> > > how
> > > > to
> > > > > > > make
> > > > > > > >> it downloadable in the easiest way.
> > > > > > > >>
> > > > > > > >> D.
> > > > > > > >>
> > > > > > > >> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
> > > > > > > sergi.vladykin@gmail.com
> > > > > > > >> >
> > > > > > > >> wrote:
> > > > > > > >>
> > > > > > > >> > Guys,
> > > > > > > >> >
> > > > > > > >> > To be honest I don't know why we choose this stack which
> is
> > > > > > completely
> > > > > > > >> > alien to java when our main product is java based. I'm
> sure
> > in
> > > > the
> > > > > > > >> future
> > > > > > > >> > we will need better level of integration between them not
> > only
> > > > for
> > > > > > > >> Ignite
> > > > > > > >> > SQL schema import.
> > > > > > > >> >
> > > > > > > >> > Jetty it is a battle tested server, I think we can go
> ahead
> > > with
> > > > > it.
> > > > > > > >> > Moreover if we will not be satisfied we can replace it
> with
> > > > > > something
> > > > > > > >> else
> > > > > > > >> > easily, while I don't know how we will replace node.js in
> a
> > > > case.
> > > > > > > >> >
> > > > > > > >> > As for JSON Alexey, please describe what kind of
> operations
> > we
> > > > do
> > > > > > with
> > > > > > > >> JSON
> > > > > > > >> > data and why we can't store it just as a String and be as
> DB
> > > > > neutral
> > > > > > > as
> > > > > > > >> > possible?
> > > > > > > >> >
> > > > > > > >> > Sergi
> > > > > > > >> >
> > > > > > > >> >
> > > > > > > >> >
> > > > > > > >> >
> > > > > > > >> >
> > > > > > > >> >
> > > > > > > >> > 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <
> > > > > akuznetsov@gridgain.com
> > > > > > >:
> > > > > > > >> >
> > > > > > > >> > > Sergey,
> > > > > > > >> > >
> > > > > > > >> > > 1. How many connections Jetty + H2 could handle?
> > > > > > > >> > > Do you have any experience?
> > > > > > > >> > >
> > > > > > > >> > > 2. What is the best way to store JSON into db and later
> > read
> > > > > JSON
> > > > > > > from
> > > > > > > >> > db?
> > > > > > > >> > >
> > > > > > > >> > > 3. Persistence feature could not be separated, because
> > > > > > > >> CacheTypeMetadata
> > > > > > > >> > is
> > > > > > > >> > > a part of CacheConfiguration.
> > > > > > > >> > >
> > > > > > > >> > > Dmitriy,
> > > > > > > >> > > What do you think about dropping nodejs and mongoDB in
> > > favor
> > > > of
> > > > > > > >> > jetty+h2 ?
> > > > > > > >> > >
> > > > > > > >> > > One more benefit of using java that we could reuse code
> > from
> > > > > > Ignite
> > > > > > > >> > Schema
> > > > > > > >> > > Import
> > > > > > > >> > > for connecting to database (using JDBC) and reuse code
> > that
> > > > > > > generates
> > > > > > > >> > XML
> > > > > > > >> > > and POJO classes.
> > > > > > > >> > >
> > > > > > > >> > > Also we could build and package Web Config with Maven I
> > > think.
> > > > > > > >> > >
> > > > > > > >> > > Actually we do not have much code at server side. So we
> > > could
> > > > > > switch
> > > > > > > >> in a
> > > > > > > >> > > couple of days I think.
> > > > > > > >> > >
> > > > > > > >> > > Thoughts?
> > > > > > > >> > >
> > > > > > > >> > >
> > > > > > > >> > > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> > > > > > > >> > sevdokimov@gridgain.com
> > > > > > > >> > > >
> > > > > > > >> > > wrote:
> > > > > > > >> > >
> > > > > > > >> > > > I doubt that people will install docker to run
> > WebConfig.
> > > > > > > >> > > >
> > > > > > > >> > > > If we expect running WebConfig on user machine
> node.js +
> > > > > mongoDB
> > > > > > > is
> > > > > > > >> a
> > > > > > > >> > bad
> > > > > > > >> > > > choose. Most of our users are java developers, the
> plain
> > > way
> > > > > is
> > > > > > to
> > > > > > > >> use
> > > > > > > >> > > > Jetty + H2 and pack whole WebConfig to single jar.
> User
> > > will
> > > > > be
> > > > > > > >> start
> > > > > > > >> > it
> > > > > > > >> > > > using "java -jar webConfig.jar" without unnecessary
> > > actions.
> > > > > > > >> > > >
> > > > > > > >> > > > As I understand, only Persistence feature requires
> > > > > installation
> > > > > > > >> > WebConfig
> > > > > > > >> > > > on local machine, my be you should create separated
> > > project
> > > > > > > >> > > > PersistenceGenerator that will use Jetty+H2 and will
> be
> > > > packed
> > > > > > to
> > > > > > > >> > single
> > > > > > > >> > > > jar.
> > > > > > > >> > > >
> > > > > > > >> > > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> > > > > > > >> > > akuznetsov@gridgain.com
> > > > > > > >> > > > >
> > > > > > > >> > > > wrote:
> > > > > > > >> > > >
> > > > > > > >> > > > > What about docker image?
> > > > > > > >> > > > > We will create docker image with installed nodejs,
> > mongo
> > > > and
> > > > > > > >> Ignite
> > > > > > > >> > Web
> > > > > > > >> > > > > Config.
> > > > > > > >> > > > > Will this solve this problem?
> > > > > > > >> > > > >
> > > > > > > >> > > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > > > > > > >> > > > dsetrakyan@apache.org>
> > > > > > > >> > > > > wrote:
> > > > > > > >> > > > >
> > > > > > > >> > > > > > From my standpoint, I would like the
> > > web-config-download
> > > > > to
> > > > > > > come
> > > > > > > >> > as a
> > > > > > > >> > > > zip
> > > > > > > >> > > > > > file without any extra installation steps if
> > possible.
> > > > > > > >> > > > > >
> > > > > > > >> > > > > > Ideally, a user should be able to just download
> it,
> > > > unzip
> > > > > > it,
> > > > > > > >> and
> > > > > > > >> > > start
> > > > > > > >> > > > > > using it.
> > > > > > > >> > > > > >
> > > > > > > >> > > > > > D.
> > > > > > > >> > > > > >
> > > > > > > >> > > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey
> Kuznetsov <
> > > > > > > >> > > > > > akuznetsov@gridgain.com>
> > > > > > > >> > > > > > wrote:
> > > > > > > >> > > > > >
> > > > > > > >> > > > > > > Igniters,
> > > > > > > >> > > > > > >
> > > > > > > >> > > > > > > We are working on Ignite Web Config (ignite-843)
> > and
> > > > > very
> > > > > > > >> close
> > > > > > > >> > to
> > > > > > > >> > > > > first
> > > > > > > >> > > > > > > version of it.
> > > > > > > >> > > > > > > As usual everything could be launched from
> > sources,
> > > > but
> > > > > > for
> > > > > > > >> > > usability
> > > > > > > >> > > > > > issue
> > > > > > > >> > > > > > > I'm thinking
> > > > > > > >> > > > > > > about a kind of installer for web config.
> > > > > > > >> > > > > > >
> > > > > > > >> > > > > > > In web config we are using: nodejs, mongodb,
> > > angular.
> > > > > > > >> > > > > > >
> > > > > > > >> > > > > > > Does any one has experience of packaging web
> > > > > applications
> > > > > > > for
> > > > > > > >> > later
> > > > > > > >> > > > > > > deployment?
> > > > > > > >> > > > > > >
> > > > > > > >> > > > > > > Any ideas are very appreciated.
> > > > > > > >> > > > > > >
> > > > > > > >> > > > > > > --
> > > > > > > >> > > > > > > Alexey Kuznetsov
> > > > > > > >> > > > > > > GridGain Systems
> > > > > > > >> > > > > > > www.gridgain.com
> > > > > > > >> > > > > > >
> > > > > > > >> > > > > >
> > > > > > > >> > > > >
> > > > > > > >> > > > >
> > > > > > > >> > > > >
> > > > > > > >> > > > > --
> > > > > > > >> > > > > Alexey Kuznetsov
> > > > > > > >> > > > > GridGain Systems
> > > > > > > >> > > > > www.gridgain.com
> > > > > > > >> > > > >
> > > > > > > >> > > >
> > > > > > > >> > >
> > > > > > > >> > >
> > > > > > > >> > >
> > > > > > > >> > > --
> > > > > > > >> > > Alexey Kuznetsov
> > > > > > > >> > > GridGain Systems
> > > > > > > >> > > www.gridgain.com
> > > > > > > >> > >
> > > > > > > >> >
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Alexey Kuznetsov
> > > > > GridGain Systems
> > > > > www.gridgain.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: Web config download
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
I think we could continue with AngularJS and Bootstrap for frontend.
On Tue, Jun 30, 2015 at 11:05 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> How about the rest of the stack?
>
> On Tue, Jun 30, 2015 at 9:03 AM, Alexey Kuznetsov <akuznetsov@gridgain.com
> >
> wrote:
>
> > If we switch for jetty - we do NOT need node.js.
> > If we switch to H2 - we do NOT need MongoDB.
> >
> > On Tue, Jun 30, 2015 at 10:52 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org
> > >
> > wrote:
> >
> > > We are still going to need node.js, right?
> > >
> > > On Tue, Jun 30, 2015 at 8:49 AM, Alexey Kuznetsov <
> > akuznetsov@gridgain.com
> > > >
> > > wrote:
> > >
> > > > Just my thoughts.
> > > >
> > > > We could implement some abstraction layer for backend persistence.
> > > > And in case of user download we will package with H2 as default
> > storage.
> > > >
> > > > But in case of heavy load any other db could be used, but will
> require
> > > > manual installation and configuration.
> > > >
> > > > We are expecting million requests per second?
> > > > I think H2 will be enough? What do you think?
> > > >
> > > >
> > > > On Tue, Jun 30, 2015 at 10:27 PM, Dmitriy Setrakyan <
> > > dsetrakyan@apache.org
> > > > >
> > > > wrote:
> > > >
> > > > > And what do you suggest we use as persistence on the backend?
> > Currently
> > > > we
> > > > > use Mongo.
> > > > >
> > > > > D.
> > > > >
> > > > > On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <
> > > > sergi.vladykin@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > And there is nothing to do from scratch here, all the html and
> > client
> > > > > side
> > > > > > js are the same, just switch backend.
> > > > > >
> > > > > > Sergi
> > > > > >
> > > > > > 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <
> sergi.vladykin@gmail.com
> > >:
> > > > > >
> > > > > > > I think at current stage if it takes two days to switch things,
> > > then
> > > > it
> > > > > > > makes sense. We will not be able to do it later.
> > > > > > >
> > > > > > > We will need to have a separate distribution for each supported
> > > > > platform.
> > > > > > > And test each individually.
> > > > > > >
> > > > > > > Sergi
> > > > > > >
> > > > > > > 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <
> > dsetrakyan@apache.org
> > > >:
> > > > > > >
> > > > > > >> Guys,
> > > > > > >>
> > > > > > >> I would like to avoid "let's drop everything and redo from
> > > scratch"
> > > > > > >> discussions. I don't think they will productively get us
> there.
> > > > > > >>
> > > > > > >> The stack was chosen because it required zero code or
> > integration
> > > on
> > > > > the
> > > > > > >> server side and was easiest to implement. Let's try to answer
> > how
> > > to
> > > > > > make
> > > > > > >> it downloadable in the easiest way.
> > > > > > >>
> > > > > > >> D.
> > > > > > >>
> > > > > > >> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
> > > > > > sergi.vladykin@gmail.com
> > > > > > >> >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >> > Guys,
> > > > > > >> >
> > > > > > >> > To be honest I don't know why we choose this stack which is
> > > > > completely
> > > > > > >> > alien to java when our main product is java based. I'm sure
> in
> > > the
> > > > > > >> future
> > > > > > >> > we will need better level of integration between them not
> only
> > > for
> > > > > > >> Ignite
> > > > > > >> > SQL schema import.
> > > > > > >> >
> > > > > > >> > Jetty it is a battle tested server, I think we can go ahead
> > with
> > > > it.
> > > > > > >> > Moreover if we will not be satisfied we can replace it with
> > > > > something
> > > > > > >> else
> > > > > > >> > easily, while I don't know how we will replace node.js in a
> > > case.
> > > > > > >> >
> > > > > > >> > As for JSON Alexey, please describe what kind of operations
> we
> > > do
> > > > > with
> > > > > > >> JSON
> > > > > > >> > data and why we can't store it just as a String and be as DB
> > > > neutral
> > > > > > as
> > > > > > >> > possible?
> > > > > > >> >
> > > > > > >> > Sergi
> > > > > > >> >
> > > > > > >> >
> > > > > > >> >
> > > > > > >> >
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <
> > > > akuznetsov@gridgain.com
> > > > > >:
> > > > > > >> >
> > > > > > >> > > Sergey,
> > > > > > >> > >
> > > > > > >> > > 1. How many connections Jetty + H2 could handle?
> > > > > > >> > > Do you have any experience?
> > > > > > >> > >
> > > > > > >> > > 2. What is the best way to store JSON into db and later
> read
> > > > JSON
> > > > > > from
> > > > > > >> > db?
> > > > > > >> > >
> > > > > > >> > > 3. Persistence feature could not be separated, because
> > > > > > >> CacheTypeMetadata
> > > > > > >> > is
> > > > > > >> > > a part of CacheConfiguration.
> > > > > > >> > >
> > > > > > >> > > Dmitriy,
> > > > > > >> > > What do you think about dropping nodejs and mongoDB in
> > favor
> > > of
> > > > > > >> > jetty+h2 ?
> > > > > > >> > >
> > > > > > >> > > One more benefit of using java that we could reuse code
> from
> > > > > Ignite
> > > > > > >> > Schema
> > > > > > >> > > Import
> > > > > > >> > > for connecting to database (using JDBC) and reuse code
> that
> > > > > > generates
> > > > > > >> > XML
> > > > > > >> > > and POJO classes.
> > > > > > >> > >
> > > > > > >> > > Also we could build and package Web Config with Maven I
> > think.
> > > > > > >> > >
> > > > > > >> > > Actually we do not have much code at server side. So we
> > could
> > > > > switch
> > > > > > >> in a
> > > > > > >> > > couple of days I think.
> > > > > > >> > >
> > > > > > >> > > Thoughts?
> > > > > > >> > >
> > > > > > >> > >
> > > > > > >> > > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> > > > > > >> > sevdokimov@gridgain.com
> > > > > > >> > > >
> > > > > > >> > > wrote:
> > > > > > >> > >
> > > > > > >> > > > I doubt that people will install docker to run
> WebConfig.
> > > > > > >> > > >
> > > > > > >> > > > If we expect running WebConfig on user machine node.js +
> > > > mongoDB
> > > > > > is
> > > > > > >> a
> > > > > > >> > bad
> > > > > > >> > > > choose. Most of our users are java developers, the plain
> > way
> > > > is
> > > > > to
> > > > > > >> use
> > > > > > >> > > > Jetty + H2 and pack whole WebConfig to single jar. User
> > will
> > > > be
> > > > > > >> start
> > > > > > >> > it
> > > > > > >> > > > using "java -jar webConfig.jar" without unnecessary
> > actions.
> > > > > > >> > > >
> > > > > > >> > > > As I understand, only Persistence feature requires
> > > > installation
> > > > > > >> > WebConfig
> > > > > > >> > > > on local machine, my be you should create separated
> > project
> > > > > > >> > > > PersistenceGenerator that will use Jetty+H2 and will be
> > > packed
> > > > > to
> > > > > > >> > single
> > > > > > >> > > > jar.
> > > > > > >> > > >
> > > > > > >> > > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> > > > > > >> > > akuznetsov@gridgain.com
> > > > > > >> > > > >
> > > > > > >> > > > wrote:
> > > > > > >> > > >
> > > > > > >> > > > > What about docker image?
> > > > > > >> > > > > We will create docker image with installed nodejs,
> mongo
> > > and
> > > > > > >> Ignite
> > > > > > >> > Web
> > > > > > >> > > > > Config.
> > > > > > >> > > > > Will this solve this problem?
> > > > > > >> > > > >
> > > > > > >> > > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > > > > > >> > > > dsetrakyan@apache.org>
> > > > > > >> > > > > wrote:
> > > > > > >> > > > >
> > > > > > >> > > > > > From my standpoint, I would like the
> > web-config-download
> > > > to
> > > > > > come
> > > > > > >> > as a
> > > > > > >> > > > zip
> > > > > > >> > > > > > file without any extra installation steps if
> possible.
> > > > > > >> > > > > >
> > > > > > >> > > > > > Ideally, a user should be able to just download it,
> > > unzip
> > > > > it,
> > > > > > >> and
> > > > > > >> > > start
> > > > > > >> > > > > > using it.
> > > > > > >> > > > > >
> > > > > > >> > > > > > D.
> > > > > > >> > > > > >
> > > > > > >> > > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > > > > > >> > > > > > akuznetsov@gridgain.com>
> > > > > > >> > > > > > wrote:
> > > > > > >> > > > > >
> > > > > > >> > > > > > > Igniters,
> > > > > > >> > > > > > >
> > > > > > >> > > > > > > We are working on Ignite Web Config (ignite-843)
> and
> > > > very
> > > > > > >> close
> > > > > > >> > to
> > > > > > >> > > > > first
> > > > > > >> > > > > > > version of it.
> > > > > > >> > > > > > > As usual everything could be launched from
> sources,
> > > but
> > > > > for
> > > > > > >> > > usability
> > > > > > >> > > > > > issue
> > > > > > >> > > > > > > I'm thinking
> > > > > > >> > > > > > > about a kind of installer for web config.
> > > > > > >> > > > > > >
> > > > > > >> > > > > > > In web config we are using: nodejs, mongodb,
> > angular.
> > > > > > >> > > > > > >
> > > > > > >> > > > > > > Does any one has experience of packaging web
> > > > applications
> > > > > > for
> > > > > > >> > later
> > > > > > >> > > > > > > deployment?
> > > > > > >> > > > > > >
> > > > > > >> > > > > > > Any ideas are very appreciated.
> > > > > > >> > > > > > >
> > > > > > >> > > > > > > --
> > > > > > >> > > > > > > Alexey Kuznetsov
> > > > > > >> > > > > > > GridGain Systems
> > > > > > >> > > > > > > www.gridgain.com
> > > > > > >> > > > > > >
> > > > > > >> > > > > >
> > > > > > >> > > > >
> > > > > > >> > > > >
> > > > > > >> > > > >
> > > > > > >> > > > > --
> > > > > > >> > > > > Alexey Kuznetsov
> > > > > > >> > > > > GridGain Systems
> > > > > > >> > > > > www.gridgain.com
> > > > > > >> > > > >
> > > > > > >> > > >
> > > > > > >> > >
> > > > > > >> > >
> > > > > > >> > >
> > > > > > >> > > --
> > > > > > >> > > Alexey Kuznetsov
> > > > > > >> > > GridGain Systems
> > > > > > >> > > www.gridgain.com
> > > > > > >> > >
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Web config download
Posted by Dmitriy Setrakyan <ds...@apache.org>.
How about the rest of the stack?
On Tue, Jun 30, 2015 at 9:03 AM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> If we switch for jetty - we do NOT need node.js.
> If we switch to H2 - we do NOT need MongoDB.
>
> On Tue, Jun 30, 2015 at 10:52 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
> >
> wrote:
>
> > We are still going to need node.js, right?
> >
> > On Tue, Jun 30, 2015 at 8:49 AM, Alexey Kuznetsov <
> akuznetsov@gridgain.com
> > >
> > wrote:
> >
> > > Just my thoughts.
> > >
> > > We could implement some abstraction layer for backend persistence.
> > > And in case of user download we will package with H2 as default
> storage.
> > >
> > > But in case of heavy load any other db could be used, but will require
> > > manual installation and configuration.
> > >
> > > We are expecting million requests per second?
> > > I think H2 will be enough? What do you think?
> > >
> > >
> > > On Tue, Jun 30, 2015 at 10:27 PM, Dmitriy Setrakyan <
> > dsetrakyan@apache.org
> > > >
> > > wrote:
> > >
> > > > And what do you suggest we use as persistence on the backend?
> Currently
> > > we
> > > > use Mongo.
> > > >
> > > > D.
> > > >
> > > > On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <
> > > sergi.vladykin@gmail.com>
> > > > wrote:
> > > >
> > > > > And there is nothing to do from scratch here, all the html and
> client
> > > > side
> > > > > js are the same, just switch backend.
> > > > >
> > > > > Sergi
> > > > >
> > > > > 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <sergi.vladykin@gmail.com
> >:
> > > > >
> > > > > > I think at current stage if it takes two days to switch things,
> > then
> > > it
> > > > > > makes sense. We will not be able to do it later.
> > > > > >
> > > > > > We will need to have a separate distribution for each supported
> > > > platform.
> > > > > > And test each individually.
> > > > > >
> > > > > > Sergi
> > > > > >
> > > > > > 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <
> dsetrakyan@apache.org
> > >:
> > > > > >
> > > > > >> Guys,
> > > > > >>
> > > > > >> I would like to avoid "let's drop everything and redo from
> > scratch"
> > > > > >> discussions. I don't think they will productively get us there.
> > > > > >>
> > > > > >> The stack was chosen because it required zero code or
> integration
> > on
> > > > the
> > > > > >> server side and was easiest to implement. Let's try to answer
> how
> > to
> > > > > make
> > > > > >> it downloadable in the easiest way.
> > > > > >>
> > > > > >> D.
> > > > > >>
> > > > > >> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
> > > > > sergi.vladykin@gmail.com
> > > > > >> >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Guys,
> > > > > >> >
> > > > > >> > To be honest I don't know why we choose this stack which is
> > > > completely
> > > > > >> > alien to java when our main product is java based. I'm sure in
> > the
> > > > > >> future
> > > > > >> > we will need better level of integration between them not only
> > for
> > > > > >> Ignite
> > > > > >> > SQL schema import.
> > > > > >> >
> > > > > >> > Jetty it is a battle tested server, I think we can go ahead
> with
> > > it.
> > > > > >> > Moreover if we will not be satisfied we can replace it with
> > > > something
> > > > > >> else
> > > > > >> > easily, while I don't know how we will replace node.js in a
> > case.
> > > > > >> >
> > > > > >> > As for JSON Alexey, please describe what kind of operations we
> > do
> > > > with
> > > > > >> JSON
> > > > > >> > data and why we can't store it just as a String and be as DB
> > > neutral
> > > > > as
> > > > > >> > possible?
> > > > > >> >
> > > > > >> > Sergi
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <
> > > akuznetsov@gridgain.com
> > > > >:
> > > > > >> >
> > > > > >> > > Sergey,
> > > > > >> > >
> > > > > >> > > 1. How many connections Jetty + H2 could handle?
> > > > > >> > > Do you have any experience?
> > > > > >> > >
> > > > > >> > > 2. What is the best way to store JSON into db and later read
> > > JSON
> > > > > from
> > > > > >> > db?
> > > > > >> > >
> > > > > >> > > 3. Persistence feature could not be separated, because
> > > > > >> CacheTypeMetadata
> > > > > >> > is
> > > > > >> > > a part of CacheConfiguration.
> > > > > >> > >
> > > > > >> > > Dmitriy,
> > > > > >> > > What do you think about dropping nodejs and mongoDB in
> favor
> > of
> > > > > >> > jetty+h2 ?
> > > > > >> > >
> > > > > >> > > One more benefit of using java that we could reuse code from
> > > > Ignite
> > > > > >> > Schema
> > > > > >> > > Import
> > > > > >> > > for connecting to database (using JDBC) and reuse code that
> > > > > generates
> > > > > >> > XML
> > > > > >> > > and POJO classes.
> > > > > >> > >
> > > > > >> > > Also we could build and package Web Config with Maven I
> think.
> > > > > >> > >
> > > > > >> > > Actually we do not have much code at server side. So we
> could
> > > > switch
> > > > > >> in a
> > > > > >> > > couple of days I think.
> > > > > >> > >
> > > > > >> > > Thoughts?
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> > > > > >> > sevdokimov@gridgain.com
> > > > > >> > > >
> > > > > >> > > wrote:
> > > > > >> > >
> > > > > >> > > > I doubt that people will install docker to run WebConfig.
> > > > > >> > > >
> > > > > >> > > > If we expect running WebConfig on user machine node.js +
> > > mongoDB
> > > > > is
> > > > > >> a
> > > > > >> > bad
> > > > > >> > > > choose. Most of our users are java developers, the plain
> way
> > > is
> > > > to
> > > > > >> use
> > > > > >> > > > Jetty + H2 and pack whole WebConfig to single jar. User
> will
> > > be
> > > > > >> start
> > > > > >> > it
> > > > > >> > > > using "java -jar webConfig.jar" without unnecessary
> actions.
> > > > > >> > > >
> > > > > >> > > > As I understand, only Persistence feature requires
> > > installation
> > > > > >> > WebConfig
> > > > > >> > > > on local machine, my be you should create separated
> project
> > > > > >> > > > PersistenceGenerator that will use Jetty+H2 and will be
> > packed
> > > > to
> > > > > >> > single
> > > > > >> > > > jar.
> > > > > >> > > >
> > > > > >> > > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> > > > > >> > > akuznetsov@gridgain.com
> > > > > >> > > > >
> > > > > >> > > > wrote:
> > > > > >> > > >
> > > > > >> > > > > What about docker image?
> > > > > >> > > > > We will create docker image with installed nodejs, mongo
> > and
> > > > > >> Ignite
> > > > > >> > Web
> > > > > >> > > > > Config.
> > > > > >> > > > > Will this solve this problem?
> > > > > >> > > > >
> > > > > >> > > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > > > > >> > > > dsetrakyan@apache.org>
> > > > > >> > > > > wrote:
> > > > > >> > > > >
> > > > > >> > > > > > From my standpoint, I would like the
> web-config-download
> > > to
> > > > > come
> > > > > >> > as a
> > > > > >> > > > zip
> > > > > >> > > > > > file without any extra installation steps if possible.
> > > > > >> > > > > >
> > > > > >> > > > > > Ideally, a user should be able to just download it,
> > unzip
> > > > it,
> > > > > >> and
> > > > > >> > > start
> > > > > >> > > > > > using it.
> > > > > >> > > > > >
> > > > > >> > > > > > D.
> > > > > >> > > > > >
> > > > > >> > > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > > > > >> > > > > > akuznetsov@gridgain.com>
> > > > > >> > > > > > wrote:
> > > > > >> > > > > >
> > > > > >> > > > > > > Igniters,
> > > > > >> > > > > > >
> > > > > >> > > > > > > We are working on Ignite Web Config (ignite-843) and
> > > very
> > > > > >> close
> > > > > >> > to
> > > > > >> > > > > first
> > > > > >> > > > > > > version of it.
> > > > > >> > > > > > > As usual everything could be launched from sources,
> > but
> > > > for
> > > > > >> > > usability
> > > > > >> > > > > > issue
> > > > > >> > > > > > > I'm thinking
> > > > > >> > > > > > > about a kind of installer for web config.
> > > > > >> > > > > > >
> > > > > >> > > > > > > In web config we are using: nodejs, mongodb,
> angular.
> > > > > >> > > > > > >
> > > > > >> > > > > > > Does any one has experience of packaging web
> > > applications
> > > > > for
> > > > > >> > later
> > > > > >> > > > > > > deployment?
> > > > > >> > > > > > >
> > > > > >> > > > > > > Any ideas are very appreciated.
> > > > > >> > > > > > >
> > > > > >> > > > > > > --
> > > > > >> > > > > > > Alexey Kuznetsov
> > > > > >> > > > > > > GridGain Systems
> > > > > >> > > > > > > www.gridgain.com
> > > > > >> > > > > > >
> > > > > >> > > > > >
> > > > > >> > > > >
> > > > > >> > > > >
> > > > > >> > > > >
> > > > > >> > > > > --
> > > > > >> > > > > Alexey Kuznetsov
> > > > > >> > > > > GridGain Systems
> > > > > >> > > > > www.gridgain.com
> > > > > >> > > > >
> > > > > >> > > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > --
> > > > > >> > > Alexey Kuznetsov
> > > > > >> > > GridGain Systems
> > > > > >> > > www.gridgain.com
> > > > > >> > >
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: Web config download
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
If we switch for jetty - we do NOT need node.js.
If we switch to H2 - we do NOT need MongoDB.
On Tue, Jun 30, 2015 at 10:52 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> We are still going to need node.js, right?
>
> On Tue, Jun 30, 2015 at 8:49 AM, Alexey Kuznetsov <akuznetsov@gridgain.com
> >
> wrote:
>
> > Just my thoughts.
> >
> > We could implement some abstraction layer for backend persistence.
> > And in case of user download we will package with H2 as default storage.
> >
> > But in case of heavy load any other db could be used, but will require
> > manual installation and configuration.
> >
> > We are expecting million requests per second?
> > I think H2 will be enough? What do you think?
> >
> >
> > On Tue, Jun 30, 2015 at 10:27 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org
> > >
> > wrote:
> >
> > > And what do you suggest we use as persistence on the backend? Currently
> > we
> > > use Mongo.
> > >
> > > D.
> > >
> > > On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <
> > sergi.vladykin@gmail.com>
> > > wrote:
> > >
> > > > And there is nothing to do from scratch here, all the html and client
> > > side
> > > > js are the same, just switch backend.
> > > >
> > > > Sergi
> > > >
> > > > 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <se...@gmail.com>:
> > > >
> > > > > I think at current stage if it takes two days to switch things,
> then
> > it
> > > > > makes sense. We will not be able to do it later.
> > > > >
> > > > > We will need to have a separate distribution for each supported
> > > platform.
> > > > > And test each individually.
> > > > >
> > > > > Sergi
> > > > >
> > > > > 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <dsetrakyan@apache.org
> >:
> > > > >
> > > > >> Guys,
> > > > >>
> > > > >> I would like to avoid "let's drop everything and redo from
> scratch"
> > > > >> discussions. I don't think they will productively get us there.
> > > > >>
> > > > >> The stack was chosen because it required zero code or integration
> on
> > > the
> > > > >> server side and was easiest to implement. Let's try to answer how
> to
> > > > make
> > > > >> it downloadable in the easiest way.
> > > > >>
> > > > >> D.
> > > > >>
> > > > >> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
> > > > sergi.vladykin@gmail.com
> > > > >> >
> > > > >> wrote:
> > > > >>
> > > > >> > Guys,
> > > > >> >
> > > > >> > To be honest I don't know why we choose this stack which is
> > > completely
> > > > >> > alien to java when our main product is java based. I'm sure in
> the
> > > > >> future
> > > > >> > we will need better level of integration between them not only
> for
> > > > >> Ignite
> > > > >> > SQL schema import.
> > > > >> >
> > > > >> > Jetty it is a battle tested server, I think we can go ahead with
> > it.
> > > > >> > Moreover if we will not be satisfied we can replace it with
> > > something
> > > > >> else
> > > > >> > easily, while I don't know how we will replace node.js in a
> case.
> > > > >> >
> > > > >> > As for JSON Alexey, please describe what kind of operations we
> do
> > > with
> > > > >> JSON
> > > > >> > data and why we can't store it just as a String and be as DB
> > neutral
> > > > as
> > > > >> > possible?
> > > > >> >
> > > > >> > Sergi
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <
> > akuznetsov@gridgain.com
> > > >:
> > > > >> >
> > > > >> > > Sergey,
> > > > >> > >
> > > > >> > > 1. How many connections Jetty + H2 could handle?
> > > > >> > > Do you have any experience?
> > > > >> > >
> > > > >> > > 2. What is the best way to store JSON into db and later read
> > JSON
> > > > from
> > > > >> > db?
> > > > >> > >
> > > > >> > > 3. Persistence feature could not be separated, because
> > > > >> CacheTypeMetadata
> > > > >> > is
> > > > >> > > a part of CacheConfiguration.
> > > > >> > >
> > > > >> > > Dmitriy,
> > > > >> > > What do you think about dropping nodejs and mongoDB in favor
> of
> > > > >> > jetty+h2 ?
> > > > >> > >
> > > > >> > > One more benefit of using java that we could reuse code from
> > > Ignite
> > > > >> > Schema
> > > > >> > > Import
> > > > >> > > for connecting to database (using JDBC) and reuse code that
> > > > generates
> > > > >> > XML
> > > > >> > > and POJO classes.
> > > > >> > >
> > > > >> > > Also we could build and package Web Config with Maven I think.
> > > > >> > >
> > > > >> > > Actually we do not have much code at server side. So we could
> > > switch
> > > > >> in a
> > > > >> > > couple of days I think.
> > > > >> > >
> > > > >> > > Thoughts?
> > > > >> > >
> > > > >> > >
> > > > >> > > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> > > > >> > sevdokimov@gridgain.com
> > > > >> > > >
> > > > >> > > wrote:
> > > > >> > >
> > > > >> > > > I doubt that people will install docker to run WebConfig.
> > > > >> > > >
> > > > >> > > > If we expect running WebConfig on user machine node.js +
> > mongoDB
> > > > is
> > > > >> a
> > > > >> > bad
> > > > >> > > > choose. Most of our users are java developers, the plain way
> > is
> > > to
> > > > >> use
> > > > >> > > > Jetty + H2 and pack whole WebConfig to single jar. User will
> > be
> > > > >> start
> > > > >> > it
> > > > >> > > > using "java -jar webConfig.jar" without unnecessary actions.
> > > > >> > > >
> > > > >> > > > As I understand, only Persistence feature requires
> > installation
> > > > >> > WebConfig
> > > > >> > > > on local machine, my be you should create separated project
> > > > >> > > > PersistenceGenerator that will use Jetty+H2 and will be
> packed
> > > to
> > > > >> > single
> > > > >> > > > jar.
> > > > >> > > >
> > > > >> > > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> > > > >> > > akuznetsov@gridgain.com
> > > > >> > > > >
> > > > >> > > > wrote:
> > > > >> > > >
> > > > >> > > > > What about docker image?
> > > > >> > > > > We will create docker image with installed nodejs, mongo
> and
> > > > >> Ignite
> > > > >> > Web
> > > > >> > > > > Config.
> > > > >> > > > > Will this solve this problem?
> > > > >> > > > >
> > > > >> > > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > > > >> > > > dsetrakyan@apache.org>
> > > > >> > > > > wrote:
> > > > >> > > > >
> > > > >> > > > > > From my standpoint, I would like the web-config-download
> > to
> > > > come
> > > > >> > as a
> > > > >> > > > zip
> > > > >> > > > > > file without any extra installation steps if possible.
> > > > >> > > > > >
> > > > >> > > > > > Ideally, a user should be able to just download it,
> unzip
> > > it,
> > > > >> and
> > > > >> > > start
> > > > >> > > > > > using it.
> > > > >> > > > > >
> > > > >> > > > > > D.
> > > > >> > > > > >
> > > > >> > > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > > > >> > > > > > akuznetsov@gridgain.com>
> > > > >> > > > > > wrote:
> > > > >> > > > > >
> > > > >> > > > > > > Igniters,
> > > > >> > > > > > >
> > > > >> > > > > > > We are working on Ignite Web Config (ignite-843) and
> > very
> > > > >> close
> > > > >> > to
> > > > >> > > > > first
> > > > >> > > > > > > version of it.
> > > > >> > > > > > > As usual everything could be launched from sources,
> but
> > > for
> > > > >> > > usability
> > > > >> > > > > > issue
> > > > >> > > > > > > I'm thinking
> > > > >> > > > > > > about a kind of installer for web config.
> > > > >> > > > > > >
> > > > >> > > > > > > In web config we are using: nodejs, mongodb, angular.
> > > > >> > > > > > >
> > > > >> > > > > > > Does any one has experience of packaging web
> > applications
> > > > for
> > > > >> > later
> > > > >> > > > > > > deployment?
> > > > >> > > > > > >
> > > > >> > > > > > > Any ideas are very appreciated.
> > > > >> > > > > > >
> > > > >> > > > > > > --
> > > > >> > > > > > > Alexey Kuznetsov
> > > > >> > > > > > > GridGain Systems
> > > > >> > > > > > > www.gridgain.com
> > > > >> > > > > > >
> > > > >> > > > > >
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > > > --
> > > > >> > > > > Alexey Kuznetsov
> > > > >> > > > > GridGain Systems
> > > > >> > > > > www.gridgain.com
> > > > >> > > > >
> > > > >> > > >
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > > --
> > > > >> > > Alexey Kuznetsov
> > > > >> > > GridGain Systems
> > > > >> > > www.gridgain.com
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Web config download
Posted by Dmitriy Setrakyan <ds...@apache.org>.
We are still going to need node.js, right?
On Tue, Jun 30, 2015 at 8:49 AM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> Just my thoughts.
>
> We could implement some abstraction layer for backend persistence.
> And in case of user download we will package with H2 as default storage.
>
> But in case of heavy load any other db could be used, but will require
> manual installation and configuration.
>
> We are expecting million requests per second?
> I think H2 will be enough? What do you think?
>
>
> On Tue, Jun 30, 2015 at 10:27 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
> >
> wrote:
>
> > And what do you suggest we use as persistence on the backend? Currently
> we
> > use Mongo.
> >
> > D.
> >
> > On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <
> sergi.vladykin@gmail.com>
> > wrote:
> >
> > > And there is nothing to do from scratch here, all the html and client
> > side
> > > js are the same, just switch backend.
> > >
> > > Sergi
> > >
> > > 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <se...@gmail.com>:
> > >
> > > > I think at current stage if it takes two days to switch things, then
> it
> > > > makes sense. We will not be able to do it later.
> > > >
> > > > We will need to have a separate distribution for each supported
> > platform.
> > > > And test each individually.
> > > >
> > > > Sergi
> > > >
> > > > 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <ds...@apache.org>:
> > > >
> > > >> Guys,
> > > >>
> > > >> I would like to avoid "let's drop everything and redo from scratch"
> > > >> discussions. I don't think they will productively get us there.
> > > >>
> > > >> The stack was chosen because it required zero code or integration on
> > the
> > > >> server side and was easiest to implement. Let's try to answer how to
> > > make
> > > >> it downloadable in the easiest way.
> > > >>
> > > >> D.
> > > >>
> > > >> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
> > > sergi.vladykin@gmail.com
> > > >> >
> > > >> wrote:
> > > >>
> > > >> > Guys,
> > > >> >
> > > >> > To be honest I don't know why we choose this stack which is
> > completely
> > > >> > alien to java when our main product is java based. I'm sure in the
> > > >> future
> > > >> > we will need better level of integration between them not only for
> > > >> Ignite
> > > >> > SQL schema import.
> > > >> >
> > > >> > Jetty it is a battle tested server, I think we can go ahead with
> it.
> > > >> > Moreover if we will not be satisfied we can replace it with
> > something
> > > >> else
> > > >> > easily, while I don't know how we will replace node.js in a case.
> > > >> >
> > > >> > As for JSON Alexey, please describe what kind of operations we do
> > with
> > > >> JSON
> > > >> > data and why we can't store it just as a String and be as DB
> neutral
> > > as
> > > >> > possible?
> > > >> >
> > > >> > Sergi
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <
> akuznetsov@gridgain.com
> > >:
> > > >> >
> > > >> > > Sergey,
> > > >> > >
> > > >> > > 1. How many connections Jetty + H2 could handle?
> > > >> > > Do you have any experience?
> > > >> > >
> > > >> > > 2. What is the best way to store JSON into db and later read
> JSON
> > > from
> > > >> > db?
> > > >> > >
> > > >> > > 3. Persistence feature could not be separated, because
> > > >> CacheTypeMetadata
> > > >> > is
> > > >> > > a part of CacheConfiguration.
> > > >> > >
> > > >> > > Dmitriy,
> > > >> > > What do you think about dropping nodejs and mongoDB in favor of
> > > >> > jetty+h2 ?
> > > >> > >
> > > >> > > One more benefit of using java that we could reuse code from
> > Ignite
> > > >> > Schema
> > > >> > > Import
> > > >> > > for connecting to database (using JDBC) and reuse code that
> > > generates
> > > >> > XML
> > > >> > > and POJO classes.
> > > >> > >
> > > >> > > Also we could build and package Web Config with Maven I think.
> > > >> > >
> > > >> > > Actually we do not have much code at server side. So we could
> > switch
> > > >> in a
> > > >> > > couple of days I think.
> > > >> > >
> > > >> > > Thoughts?
> > > >> > >
> > > >> > >
> > > >> > > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> > > >> > sevdokimov@gridgain.com
> > > >> > > >
> > > >> > > wrote:
> > > >> > >
> > > >> > > > I doubt that people will install docker to run WebConfig.
> > > >> > > >
> > > >> > > > If we expect running WebConfig on user machine node.js +
> mongoDB
> > > is
> > > >> a
> > > >> > bad
> > > >> > > > choose. Most of our users are java developers, the plain way
> is
> > to
> > > >> use
> > > >> > > > Jetty + H2 and pack whole WebConfig to single jar. User will
> be
> > > >> start
> > > >> > it
> > > >> > > > using "java -jar webConfig.jar" without unnecessary actions.
> > > >> > > >
> > > >> > > > As I understand, only Persistence feature requires
> installation
> > > >> > WebConfig
> > > >> > > > on local machine, my be you should create separated project
> > > >> > > > PersistenceGenerator that will use Jetty+H2 and will be packed
> > to
> > > >> > single
> > > >> > > > jar.
> > > >> > > >
> > > >> > > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> > > >> > > akuznetsov@gridgain.com
> > > >> > > > >
> > > >> > > > wrote:
> > > >> > > >
> > > >> > > > > What about docker image?
> > > >> > > > > We will create docker image with installed nodejs, mongo and
> > > >> Ignite
> > > >> > Web
> > > >> > > > > Config.
> > > >> > > > > Will this solve this problem?
> > > >> > > > >
> > > >> > > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > > >> > > > dsetrakyan@apache.org>
> > > >> > > > > wrote:
> > > >> > > > >
> > > >> > > > > > From my standpoint, I would like the web-config-download
> to
> > > come
> > > >> > as a
> > > >> > > > zip
> > > >> > > > > > file without any extra installation steps if possible.
> > > >> > > > > >
> > > >> > > > > > Ideally, a user should be able to just download it, unzip
> > it,
> > > >> and
> > > >> > > start
> > > >> > > > > > using it.
> > > >> > > > > >
> > > >> > > > > > D.
> > > >> > > > > >
> > > >> > > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > > >> > > > > > akuznetsov@gridgain.com>
> > > >> > > > > > wrote:
> > > >> > > > > >
> > > >> > > > > > > Igniters,
> > > >> > > > > > >
> > > >> > > > > > > We are working on Ignite Web Config (ignite-843) and
> very
> > > >> close
> > > >> > to
> > > >> > > > > first
> > > >> > > > > > > version of it.
> > > >> > > > > > > As usual everything could be launched from sources, but
> > for
> > > >> > > usability
> > > >> > > > > > issue
> > > >> > > > > > > I'm thinking
> > > >> > > > > > > about a kind of installer for web config.
> > > >> > > > > > >
> > > >> > > > > > > In web config we are using: nodejs, mongodb, angular.
> > > >> > > > > > >
> > > >> > > > > > > Does any one has experience of packaging web
> applications
> > > for
> > > >> > later
> > > >> > > > > > > deployment?
> > > >> > > > > > >
> > > >> > > > > > > Any ideas are very appreciated.
> > > >> > > > > > >
> > > >> > > > > > > --
> > > >> > > > > > > Alexey Kuznetsov
> > > >> > > > > > > GridGain Systems
> > > >> > > > > > > www.gridgain.com
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > --
> > > >> > > > > Alexey Kuznetsov
> > > >> > > > > GridGain Systems
> > > >> > > > > www.gridgain.com
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Alexey Kuznetsov
> > > >> > > GridGain Systems
> > > >> > > www.gridgain.com
> > > >> > >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: Web config download
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
Just my thoughts.
We could implement some abstraction layer for backend persistence.
And in case of user download we will package with H2 as default storage.
But in case of heavy load any other db could be used, but will require
manual installation and configuration.
We are expecting million requests per second?
I think H2 will be enough? What do you think?
On Tue, Jun 30, 2015 at 10:27 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> And what do you suggest we use as persistence on the backend? Currently we
> use Mongo.
>
> D.
>
> On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <se...@gmail.com>
> wrote:
>
> > And there is nothing to do from scratch here, all the html and client
> side
> > js are the same, just switch backend.
> >
> > Sergi
> >
> > 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <se...@gmail.com>:
> >
> > > I think at current stage if it takes two days to switch things, then it
> > > makes sense. We will not be able to do it later.
> > >
> > > We will need to have a separate distribution for each supported
> platform.
> > > And test each individually.
> > >
> > > Sergi
> > >
> > > 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <ds...@apache.org>:
> > >
> > >> Guys,
> > >>
> > >> I would like to avoid "let's drop everything and redo from scratch"
> > >> discussions. I don't think they will productively get us there.
> > >>
> > >> The stack was chosen because it required zero code or integration on
> the
> > >> server side and was easiest to implement. Let's try to answer how to
> > make
> > >> it downloadable in the easiest way.
> > >>
> > >> D.
> > >>
> > >> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
> > sergi.vladykin@gmail.com
> > >> >
> > >> wrote:
> > >>
> > >> > Guys,
> > >> >
> > >> > To be honest I don't know why we choose this stack which is
> completely
> > >> > alien to java when our main product is java based. I'm sure in the
> > >> future
> > >> > we will need better level of integration between them not only for
> > >> Ignite
> > >> > SQL schema import.
> > >> >
> > >> > Jetty it is a battle tested server, I think we can go ahead with it.
> > >> > Moreover if we will not be satisfied we can replace it with
> something
> > >> else
> > >> > easily, while I don't know how we will replace node.js in a case.
> > >> >
> > >> > As for JSON Alexey, please describe what kind of operations we do
> with
> > >> JSON
> > >> > data and why we can't store it just as a String and be as DB neutral
> > as
> > >> > possible?
> > >> >
> > >> > Sergi
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <akuznetsov@gridgain.com
> >:
> > >> >
> > >> > > Sergey,
> > >> > >
> > >> > > 1. How many connections Jetty + H2 could handle?
> > >> > > Do you have any experience?
> > >> > >
> > >> > > 2. What is the best way to store JSON into db and later read JSON
> > from
> > >> > db?
> > >> > >
> > >> > > 3. Persistence feature could not be separated, because
> > >> CacheTypeMetadata
> > >> > is
> > >> > > a part of CacheConfiguration.
> > >> > >
> > >> > > Dmitriy,
> > >> > > What do you think about dropping nodejs and mongoDB in favor of
> > >> > jetty+h2 ?
> > >> > >
> > >> > > One more benefit of using java that we could reuse code from
> Ignite
> > >> > Schema
> > >> > > Import
> > >> > > for connecting to database (using JDBC) and reuse code that
> > generates
> > >> > XML
> > >> > > and POJO classes.
> > >> > >
> > >> > > Also we could build and package Web Config with Maven I think.
> > >> > >
> > >> > > Actually we do not have much code at server side. So we could
> switch
> > >> in a
> > >> > > couple of days I think.
> > >> > >
> > >> > > Thoughts?
> > >> > >
> > >> > >
> > >> > > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> > >> > sevdokimov@gridgain.com
> > >> > > >
> > >> > > wrote:
> > >> > >
> > >> > > > I doubt that people will install docker to run WebConfig.
> > >> > > >
> > >> > > > If we expect running WebConfig on user machine node.js + mongoDB
> > is
> > >> a
> > >> > bad
> > >> > > > choose. Most of our users are java developers, the plain way is
> to
> > >> use
> > >> > > > Jetty + H2 and pack whole WebConfig to single jar. User will be
> > >> start
> > >> > it
> > >> > > > using "java -jar webConfig.jar" without unnecessary actions.
> > >> > > >
> > >> > > > As I understand, only Persistence feature requires installation
> > >> > WebConfig
> > >> > > > on local machine, my be you should create separated project
> > >> > > > PersistenceGenerator that will use Jetty+H2 and will be packed
> to
> > >> > single
> > >> > > > jar.
> > >> > > >
> > >> > > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> > >> > > akuznetsov@gridgain.com
> > >> > > > >
> > >> > > > wrote:
> > >> > > >
> > >> > > > > What about docker image?
> > >> > > > > We will create docker image with installed nodejs, mongo and
> > >> Ignite
> > >> > Web
> > >> > > > > Config.
> > >> > > > > Will this solve this problem?
> > >> > > > >
> > >> > > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > >> > > > dsetrakyan@apache.org>
> > >> > > > > wrote:
> > >> > > > >
> > >> > > > > > From my standpoint, I would like the web-config-download to
> > come
> > >> > as a
> > >> > > > zip
> > >> > > > > > file without any extra installation steps if possible.
> > >> > > > > >
> > >> > > > > > Ideally, a user should be able to just download it, unzip
> it,
> > >> and
> > >> > > start
> > >> > > > > > using it.
> > >> > > > > >
> > >> > > > > > D.
> > >> > > > > >
> > >> > > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > >> > > > > > akuznetsov@gridgain.com>
> > >> > > > > > wrote:
> > >> > > > > >
> > >> > > > > > > Igniters,
> > >> > > > > > >
> > >> > > > > > > We are working on Ignite Web Config (ignite-843) and very
> > >> close
> > >> > to
> > >> > > > > first
> > >> > > > > > > version of it.
> > >> > > > > > > As usual everything could be launched from sources, but
> for
> > >> > > usability
> > >> > > > > > issue
> > >> > > > > > > I'm thinking
> > >> > > > > > > about a kind of installer for web config.
> > >> > > > > > >
> > >> > > > > > > In web config we are using: nodejs, mongodb, angular.
> > >> > > > > > >
> > >> > > > > > > Does any one has experience of packaging web applications
> > for
> > >> > later
> > >> > > > > > > deployment?
> > >> > > > > > >
> > >> > > > > > > Any ideas are very appreciated.
> > >> > > > > > >
> > >> > > > > > > --
> > >> > > > > > > Alexey Kuznetsov
> > >> > > > > > > GridGain Systems
> > >> > > > > > > www.gridgain.com
> > >> > > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> > > > > --
> > >> > > > > Alexey Kuznetsov
> > >> > > > > GridGain Systems
> > >> > > > > www.gridgain.com
> > >> > > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > Alexey Kuznetsov
> > >> > > GridGain Systems
> > >> > > www.gridgain.com
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Web config download
Posted by Dmitriy Setrakyan <ds...@apache.org>.
And what do you suggest we use as persistence on the backend? Currently we
use Mongo.
D.
On Tue, Jun 30, 2015 at 8:18 AM, Sergi Vladykin <se...@gmail.com>
wrote:
> And there is nothing to do from scratch here, all the html and client side
> js are the same, just switch backend.
>
> Sergi
>
> 2015-06-30 8:17 GMT-07:00 Sergi Vladykin <se...@gmail.com>:
>
> > I think at current stage if it takes two days to switch things, then it
> > makes sense. We will not be able to do it later.
> >
> > We will need to have a separate distribution for each supported platform.
> > And test each individually.
> >
> > Sergi
> >
> > 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <ds...@apache.org>:
> >
> >> Guys,
> >>
> >> I would like to avoid "let's drop everything and redo from scratch"
> >> discussions. I don't think they will productively get us there.
> >>
> >> The stack was chosen because it required zero code or integration on the
> >> server side and was easiest to implement. Let's try to answer how to
> make
> >> it downloadable in the easiest way.
> >>
> >> D.
> >>
> >> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <
> sergi.vladykin@gmail.com
> >> >
> >> wrote:
> >>
> >> > Guys,
> >> >
> >> > To be honest I don't know why we choose this stack which is completely
> >> > alien to java when our main product is java based. I'm sure in the
> >> future
> >> > we will need better level of integration between them not only for
> >> Ignite
> >> > SQL schema import.
> >> >
> >> > Jetty it is a battle tested server, I think we can go ahead with it.
> >> > Moreover if we will not be satisfied we can replace it with something
> >> else
> >> > easily, while I don't know how we will replace node.js in a case.
> >> >
> >> > As for JSON Alexey, please describe what kind of operations we do with
> >> JSON
> >> > data and why we can't store it just as a String and be as DB neutral
> as
> >> > possible?
> >> >
> >> > Sergi
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <ak...@gridgain.com>:
> >> >
> >> > > Sergey,
> >> > >
> >> > > 1. How many connections Jetty + H2 could handle?
> >> > > Do you have any experience?
> >> > >
> >> > > 2. What is the best way to store JSON into db and later read JSON
> from
> >> > db?
> >> > >
> >> > > 3. Persistence feature could not be separated, because
> >> CacheTypeMetadata
> >> > is
> >> > > a part of CacheConfiguration.
> >> > >
> >> > > Dmitriy,
> >> > > What do you think about dropping nodejs and mongoDB in favor of
> >> > jetty+h2 ?
> >> > >
> >> > > One more benefit of using java that we could reuse code from Ignite
> >> > Schema
> >> > > Import
> >> > > for connecting to database (using JDBC) and reuse code that
> generates
> >> > XML
> >> > > and POJO classes.
> >> > >
> >> > > Also we could build and package Web Config with Maven I think.
> >> > >
> >> > > Actually we do not have much code at server side. So we could switch
> >> in a
> >> > > couple of days I think.
> >> > >
> >> > > Thoughts?
> >> > >
> >> > >
> >> > > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> >> > sevdokimov@gridgain.com
> >> > > >
> >> > > wrote:
> >> > >
> >> > > > I doubt that people will install docker to run WebConfig.
> >> > > >
> >> > > > If we expect running WebConfig on user machine node.js + mongoDB
> is
> >> a
> >> > bad
> >> > > > choose. Most of our users are java developers, the plain way is to
> >> use
> >> > > > Jetty + H2 and pack whole WebConfig to single jar. User will be
> >> start
> >> > it
> >> > > > using "java -jar webConfig.jar" without unnecessary actions.
> >> > > >
> >> > > > As I understand, only Persistence feature requires installation
> >> > WebConfig
> >> > > > on local machine, my be you should create separated project
> >> > > > PersistenceGenerator that will use Jetty+H2 and will be packed to
> >> > single
> >> > > > jar.
> >> > > >
> >> > > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> >> > > akuznetsov@gridgain.com
> >> > > > >
> >> > > > wrote:
> >> > > >
> >> > > > > What about docker image?
> >> > > > > We will create docker image with installed nodejs, mongo and
> >> Ignite
> >> > Web
> >> > > > > Config.
> >> > > > > Will this solve this problem?
> >> > > > >
> >> > > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> >> > > > dsetrakyan@apache.org>
> >> > > > > wrote:
> >> > > > >
> >> > > > > > From my standpoint, I would like the web-config-download to
> come
> >> > as a
> >> > > > zip
> >> > > > > > file without any extra installation steps if possible.
> >> > > > > >
> >> > > > > > Ideally, a user should be able to just download it, unzip it,
> >> and
> >> > > start
> >> > > > > > using it.
> >> > > > > >
> >> > > > > > D.
> >> > > > > >
> >> > > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> >> > > > > > akuznetsov@gridgain.com>
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > Igniters,
> >> > > > > > >
> >> > > > > > > We are working on Ignite Web Config (ignite-843) and very
> >> close
> >> > to
> >> > > > > first
> >> > > > > > > version of it.
> >> > > > > > > As usual everything could be launched from sources, but for
> >> > > usability
> >> > > > > > issue
> >> > > > > > > I'm thinking
> >> > > > > > > about a kind of installer for web config.
> >> > > > > > >
> >> > > > > > > In web config we are using: nodejs, mongodb, angular.
> >> > > > > > >
> >> > > > > > > Does any one has experience of packaging web applications
> for
> >> > later
> >> > > > > > > deployment?
> >> > > > > > >
> >> > > > > > > Any ideas are very appreciated.
> >> > > > > > >
> >> > > > > > > --
> >> > > > > > > Alexey Kuznetsov
> >> > > > > > > GridGain Systems
> >> > > > > > > www.gridgain.com
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > --
> >> > > > > Alexey Kuznetsov
> >> > > > > GridGain Systems
> >> > > > > www.gridgain.com
> >> > > > >
> >> > > >
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > Alexey Kuznetsov
> >> > > GridGain Systems
> >> > > www.gridgain.com
> >> > >
> >> >
> >>
> >
> >
>
Re: Web config download
Posted by Sergi Vladykin <se...@gmail.com>.
And there is nothing to do from scratch here, all the html and client side
js are the same, just switch backend.
Sergi
2015-06-30 8:17 GMT-07:00 Sergi Vladykin <se...@gmail.com>:
> I think at current stage if it takes two days to switch things, then it
> makes sense. We will not be able to do it later.
>
> We will need to have a separate distribution for each supported platform.
> And test each individually.
>
> Sergi
>
> 2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <ds...@apache.org>:
>
>> Guys,
>>
>> I would like to avoid "let's drop everything and redo from scratch"
>> discussions. I don't think they will productively get us there.
>>
>> The stack was chosen because it required zero code or integration on the
>> server side and was easiest to implement. Let's try to answer how to make
>> it downloadable in the easiest way.
>>
>> D.
>>
>> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <sergi.vladykin@gmail.com
>> >
>> wrote:
>>
>> > Guys,
>> >
>> > To be honest I don't know why we choose this stack which is completely
>> > alien to java when our main product is java based. I'm sure in the
>> future
>> > we will need better level of integration between them not only for
>> Ignite
>> > SQL schema import.
>> >
>> > Jetty it is a battle tested server, I think we can go ahead with it.
>> > Moreover if we will not be satisfied we can replace it with something
>> else
>> > easily, while I don't know how we will replace node.js in a case.
>> >
>> > As for JSON Alexey, please describe what kind of operations we do with
>> JSON
>> > data and why we can't store it just as a String and be as DB neutral as
>> > possible?
>> >
>> > Sergi
>> >
>> >
>> >
>> >
>> >
>> >
>> > 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <ak...@gridgain.com>:
>> >
>> > > Sergey,
>> > >
>> > > 1. How many connections Jetty + H2 could handle?
>> > > Do you have any experience?
>> > >
>> > > 2. What is the best way to store JSON into db and later read JSON from
>> > db?
>> > >
>> > > 3. Persistence feature could not be separated, because
>> CacheTypeMetadata
>> > is
>> > > a part of CacheConfiguration.
>> > >
>> > > Dmitriy,
>> > > What do you think about dropping nodejs and mongoDB in favor of
>> > jetty+h2 ?
>> > >
>> > > One more benefit of using java that we could reuse code from Ignite
>> > Schema
>> > > Import
>> > > for connecting to database (using JDBC) and reuse code that generates
>> > XML
>> > > and POJO classes.
>> > >
>> > > Also we could build and package Web Config with Maven I think.
>> > >
>> > > Actually we do not have much code at server side. So we could switch
>> in a
>> > > couple of days I think.
>> > >
>> > > Thoughts?
>> > >
>> > >
>> > > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
>> > sevdokimov@gridgain.com
>> > > >
>> > > wrote:
>> > >
>> > > > I doubt that people will install docker to run WebConfig.
>> > > >
>> > > > If we expect running WebConfig on user machine node.js + mongoDB is
>> a
>> > bad
>> > > > choose. Most of our users are java developers, the plain way is to
>> use
>> > > > Jetty + H2 and pack whole WebConfig to single jar. User will be
>> start
>> > it
>> > > > using "java -jar webConfig.jar" without unnecessary actions.
>> > > >
>> > > > As I understand, only Persistence feature requires installation
>> > WebConfig
>> > > > on local machine, my be you should create separated project
>> > > > PersistenceGenerator that will use Jetty+H2 and will be packed to
>> > single
>> > > > jar.
>> > > >
>> > > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
>> > > akuznetsov@gridgain.com
>> > > > >
>> > > > wrote:
>> > > >
>> > > > > What about docker image?
>> > > > > We will create docker image with installed nodejs, mongo and
>> Ignite
>> > Web
>> > > > > Config.
>> > > > > Will this solve this problem?
>> > > > >
>> > > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
>> > > > dsetrakyan@apache.org>
>> > > > > wrote:
>> > > > >
>> > > > > > From my standpoint, I would like the web-config-download to come
>> > as a
>> > > > zip
>> > > > > > file without any extra installation steps if possible.
>> > > > > >
>> > > > > > Ideally, a user should be able to just download it, unzip it,
>> and
>> > > start
>> > > > > > using it.
>> > > > > >
>> > > > > > D.
>> > > > > >
>> > > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
>> > > > > > akuznetsov@gridgain.com>
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Igniters,
>> > > > > > >
>> > > > > > > We are working on Ignite Web Config (ignite-843) and very
>> close
>> > to
>> > > > > first
>> > > > > > > version of it.
>> > > > > > > As usual everything could be launched from sources, but for
>> > > usability
>> > > > > > issue
>> > > > > > > I'm thinking
>> > > > > > > about a kind of installer for web config.
>> > > > > > >
>> > > > > > > In web config we are using: nodejs, mongodb, angular.
>> > > > > > >
>> > > > > > > Does any one has experience of packaging web applications for
>> > later
>> > > > > > > deployment?
>> > > > > > >
>> > > > > > > Any ideas are very appreciated.
>> > > > > > >
>> > > > > > > --
>> > > > > > > Alexey Kuznetsov
>> > > > > > > GridGain Systems
>> > > > > > > www.gridgain.com
>> > > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Alexey Kuznetsov
>> > > > > GridGain Systems
>> > > > > www.gridgain.com
>> > > > >
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Alexey Kuznetsov
>> > > GridGain Systems
>> > > www.gridgain.com
>> > >
>> >
>>
>
>
Re: Web config download
Posted by Sergi Vladykin <se...@gmail.com>.
I think at current stage if it takes two days to switch things, then it
makes sense. We will not be able to do it later.
We will need to have a separate distribution for each supported platform.
And test each individually.
Sergi
2015-06-30 8:05 GMT-07:00 Dmitriy Setrakyan <ds...@apache.org>:
> Guys,
>
> I would like to avoid "let's drop everything and redo from scratch"
> discussions. I don't think they will productively get us there.
>
> The stack was chosen because it required zero code or integration on the
> server side and was easiest to implement. Let's try to answer how to make
> it downloadable in the easiest way.
>
> D.
>
> On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <se...@gmail.com>
> wrote:
>
> > Guys,
> >
> > To be honest I don't know why we choose this stack which is completely
> > alien to java when our main product is java based. I'm sure in the future
> > we will need better level of integration between them not only for Ignite
> > SQL schema import.
> >
> > Jetty it is a battle tested server, I think we can go ahead with it.
> > Moreover if we will not be satisfied we can replace it with something
> else
> > easily, while I don't know how we will replace node.js in a case.
> >
> > As for JSON Alexey, please describe what kind of operations we do with
> JSON
> > data and why we can't store it just as a String and be as DB neutral as
> > possible?
> >
> > Sergi
> >
> >
> >
> >
> >
> >
> > 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <ak...@gridgain.com>:
> >
> > > Sergey,
> > >
> > > 1. How many connections Jetty + H2 could handle?
> > > Do you have any experience?
> > >
> > > 2. What is the best way to store JSON into db and later read JSON from
> > db?
> > >
> > > 3. Persistence feature could not be separated, because
> CacheTypeMetadata
> > is
> > > a part of CacheConfiguration.
> > >
> > > Dmitriy,
> > > What do you think about dropping nodejs and mongoDB in favor of
> > jetty+h2 ?
> > >
> > > One more benefit of using java that we could reuse code from Ignite
> > Schema
> > > Import
> > > for connecting to database (using JDBC) and reuse code that generates
> > XML
> > > and POJO classes.
> > >
> > > Also we could build and package Web Config with Maven I think.
> > >
> > > Actually we do not have much code at server side. So we could switch
> in a
> > > couple of days I think.
> > >
> > > Thoughts?
> > >
> > >
> > > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> > sevdokimov@gridgain.com
> > > >
> > > wrote:
> > >
> > > > I doubt that people will install docker to run WebConfig.
> > > >
> > > > If we expect running WebConfig on user machine node.js + mongoDB is a
> > bad
> > > > choose. Most of our users are java developers, the plain way is to
> use
> > > > Jetty + H2 and pack whole WebConfig to single jar. User will be start
> > it
> > > > using "java -jar webConfig.jar" without unnecessary actions.
> > > >
> > > > As I understand, only Persistence feature requires installation
> > WebConfig
> > > > on local machine, my be you should create separated project
> > > > PersistenceGenerator that will use Jetty+H2 and will be packed to
> > single
> > > > jar.
> > > >
> > > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> > > akuznetsov@gridgain.com
> > > > >
> > > > wrote:
> > > >
> > > > > What about docker image?
> > > > > We will create docker image with installed nodejs, mongo and Ignite
> > Web
> > > > > Config.
> > > > > Will this solve this problem?
> > > > >
> > > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > > > dsetrakyan@apache.org>
> > > > > wrote:
> > > > >
> > > > > > From my standpoint, I would like the web-config-download to come
> > as a
> > > > zip
> > > > > > file without any extra installation steps if possible.
> > > > > >
> > > > > > Ideally, a user should be able to just download it, unzip it, and
> > > start
> > > > > > using it.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > > > > > akuznetsov@gridgain.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Igniters,
> > > > > > >
> > > > > > > We are working on Ignite Web Config (ignite-843) and very close
> > to
> > > > > first
> > > > > > > version of it.
> > > > > > > As usual everything could be launched from sources, but for
> > > usability
> > > > > > issue
> > > > > > > I'm thinking
> > > > > > > about a kind of installer for web config.
> > > > > > >
> > > > > > > In web config we are using: nodejs, mongodb, angular.
> > > > > > >
> > > > > > > Does any one has experience of packaging web applications for
> > later
> > > > > > > deployment?
> > > > > > >
> > > > > > > Any ideas are very appreciated.
> > > > > > >
> > > > > > > --
> > > > > > > Alexey Kuznetsov
> > > > > > > GridGain Systems
> > > > > > > www.gridgain.com
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Alexey Kuznetsov
> > > > > GridGain Systems
> > > > > www.gridgain.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
Re: Web config download
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Guys,
I would like to avoid "let's drop everything and redo from scratch"
discussions. I don't think they will productively get us there.
The stack was chosen because it required zero code or integration on the
server side and was easiest to implement. Let's try to answer how to make
it downloadable in the easiest way.
D.
On Tue, Jun 30, 2015 at 7:52 AM, Sergi Vladykin <se...@gmail.com>
wrote:
> Guys,
>
> To be honest I don't know why we choose this stack which is completely
> alien to java when our main product is java based. I'm sure in the future
> we will need better level of integration between them not only for Ignite
> SQL schema import.
>
> Jetty it is a battle tested server, I think we can go ahead with it.
> Moreover if we will not be satisfied we can replace it with something else
> easily, while I don't know how we will replace node.js in a case.
>
> As for JSON Alexey, please describe what kind of operations we do with JSON
> data and why we can't store it just as a String and be as DB neutral as
> possible?
>
> Sergi
>
>
>
>
>
>
> 2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <ak...@gridgain.com>:
>
> > Sergey,
> >
> > 1. How many connections Jetty + H2 could handle?
> > Do you have any experience?
> >
> > 2. What is the best way to store JSON into db and later read JSON from
> db?
> >
> > 3. Persistence feature could not be separated, because CacheTypeMetadata
> is
> > a part of CacheConfiguration.
> >
> > Dmitriy,
> > What do you think about dropping nodejs and mongoDB in favor of
> jetty+h2 ?
> >
> > One more benefit of using java that we could reuse code from Ignite
> Schema
> > Import
> > for connecting to database (using JDBC) and reuse code that generates
> XML
> > and POJO classes.
> >
> > Also we could build and package Web Config with Maven I think.
> >
> > Actually we do not have much code at server side. So we could switch in a
> > couple of days I think.
> >
> > Thoughts?
> >
> >
> > On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <
> sevdokimov@gridgain.com
> > >
> > wrote:
> >
> > > I doubt that people will install docker to run WebConfig.
> > >
> > > If we expect running WebConfig on user machine node.js + mongoDB is a
> bad
> > > choose. Most of our users are java developers, the plain way is to use
> > > Jetty + H2 and pack whole WebConfig to single jar. User will be start
> it
> > > using "java -jar webConfig.jar" without unnecessary actions.
> > >
> > > As I understand, only Persistence feature requires installation
> WebConfig
> > > on local machine, my be you should create separated project
> > > PersistenceGenerator that will use Jetty+H2 and will be packed to
> single
> > > jar.
> > >
> > > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> > akuznetsov@gridgain.com
> > > >
> > > wrote:
> > >
> > > > What about docker image?
> > > > We will create docker image with installed nodejs, mongo and Ignite
> Web
> > > > Config.
> > > > Will this solve this problem?
> > > >
> > > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > > dsetrakyan@apache.org>
> > > > wrote:
> > > >
> > > > > From my standpoint, I would like the web-config-download to come
> as a
> > > zip
> > > > > file without any extra installation steps if possible.
> > > > >
> > > > > Ideally, a user should be able to just download it, unzip it, and
> > start
> > > > > using it.
> > > > >
> > > > > D.
> > > > >
> > > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > > > > akuznetsov@gridgain.com>
> > > > > wrote:
> > > > >
> > > > > > Igniters,
> > > > > >
> > > > > > We are working on Ignite Web Config (ignite-843) and very close
> to
> > > > first
> > > > > > version of it.
> > > > > > As usual everything could be launched from sources, but for
> > usability
> > > > > issue
> > > > > > I'm thinking
> > > > > > about a kind of installer for web config.
> > > > > >
> > > > > > In web config we are using: nodejs, mongodb, angular.
> > > > > >
> > > > > > Does any one has experience of packaging web applications for
> later
> > > > > > deployment?
> > > > > >
> > > > > > Any ideas are very appreciated.
> > > > > >
> > > > > > --
> > > > > > Alexey Kuznetsov
> > > > > > GridGain Systems
> > > > > > www.gridgain.com
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>
Re: Web config download
Posted by Sergi Vladykin <se...@gmail.com>.
Guys,
To be honest I don't know why we choose this stack which is completely
alien to java when our main product is java based. I'm sure in the future
we will need better level of integration between them not only for Ignite
SQL schema import.
Jetty it is a battle tested server, I think we can go ahead with it.
Moreover if we will not be satisfied we can replace it with something else
easily, while I don't know how we will replace node.js in a case.
As for JSON Alexey, please describe what kind of operations we do with JSON
data and why we can't store it just as a String and be as DB neutral as
possible?
Sergi
2015-06-30 7:31 GMT-07:00 Alexey Kuznetsov <ak...@gridgain.com>:
> Sergey,
>
> 1. How many connections Jetty + H2 could handle?
> Do you have any experience?
>
> 2. What is the best way to store JSON into db and later read JSON from db?
>
> 3. Persistence feature could not be separated, because CacheTypeMetadata is
> a part of CacheConfiguration.
>
> Dmitriy,
> What do you think about dropping nodejs and mongoDB in favor of jetty+h2 ?
>
> One more benefit of using java that we could reuse code from Ignite Schema
> Import
> for connecting to database (using JDBC) and reuse code that generates XML
> and POJO classes.
>
> Also we could build and package Web Config with Maven I think.
>
> Actually we do not have much code at server side. So we could switch in a
> couple of days I think.
>
> Thoughts?
>
>
> On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <sevdokimov@gridgain.com
> >
> wrote:
>
> > I doubt that people will install docker to run WebConfig.
> >
> > If we expect running WebConfig on user machine node.js + mongoDB is a bad
> > choose. Most of our users are java developers, the plain way is to use
> > Jetty + H2 and pack whole WebConfig to single jar. User will be start it
> > using "java -jar webConfig.jar" without unnecessary actions.
> >
> > As I understand, only Persistence feature requires installation WebConfig
> > on local machine, my be you should create separated project
> > PersistenceGenerator that will use Jetty+H2 and will be packed to single
> > jar.
> >
> > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> akuznetsov@gridgain.com
> > >
> > wrote:
> >
> > > What about docker image?
> > > We will create docker image with installed nodejs, mongo and Ignite Web
> > > Config.
> > > Will this solve this problem?
> > >
> > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > dsetrakyan@apache.org>
> > > wrote:
> > >
> > > > From my standpoint, I would like the web-config-download to come as a
> > zip
> > > > file without any extra installation steps if possible.
> > > >
> > > > Ideally, a user should be able to just download it, unzip it, and
> start
> > > > using it.
> > > >
> > > > D.
> > > >
> > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > > > akuznetsov@gridgain.com>
> > > > wrote:
> > > >
> > > > > Igniters,
> > > > >
> > > > > We are working on Ignite Web Config (ignite-843) and very close to
> > > first
> > > > > version of it.
> > > > > As usual everything could be launched from sources, but for
> usability
> > > > issue
> > > > > I'm thinking
> > > > > about a kind of installer for web config.
> > > > >
> > > > > In web config we are using: nodejs, mongodb, angular.
> > > > >
> > > > > Does any one has experience of packaging web applications for later
> > > > > deployment?
> > > > >
> > > > > Any ideas are very appreciated.
> > > > >
> > > > > --
> > > > > Alexey Kuznetsov
> > > > > GridGain Systems
> > > > > www.gridgain.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: Web config download
Posted by Sergey Evdokimov <se...@gridgain.com>.
> 1. How many connections Jetty + H2 could handle?
> Do you have any experience?
I didn't use Jetty for production deployment, but there is no problem with
high load:
http://stackoverflow.com/questions/3834599/is-jetty-ever-used-for-production-deployment
> 2. What is the best way to store JSON into db and later read JSON from db?
What the JSON ? WebConfig stores Ignite configuration, it's a Java object.
Using unknown technology like Node.js slowly development a lot. It is a
pity to waste time learning Node.js as I will never use it in the future.
Node.js is not in java world, java developers write server side on java,
not on JavaScript.
On Tue, Jun 30, 2015 at 5:31 PM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> Sergey,
>
> 1. How many connections Jetty + H2 could handle?
> Do you have any experience?
>
> 2. What is the best way to store JSON into db and later read JSON from db?
>
> 3. Persistence feature could not be separated, because CacheTypeMetadata is
> a part of CacheConfiguration.
>
> Dmitriy,
> What do you think about dropping nodejs and mongoDB in favor of jetty+h2 ?
>
> One more benefit of using java that we could reuse code from Ignite Schema
> Import
> for connecting to database (using JDBC) and reuse code that generates XML
> and POJO classes.
>
> Also we could build and package Web Config with Maven I think.
>
> Actually we do not have much code at server side. So we could switch in a
> couple of days I think.
>
> Thoughts?
>
>
> On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <sevdokimov@gridgain.com
> >
> wrote:
>
> > I doubt that people will install docker to run WebConfig.
> >
> > If we expect running WebConfig on user machine node.js + mongoDB is a bad
> > choose. Most of our users are java developers, the plain way is to use
> > Jetty + H2 and pack whole WebConfig to single jar. User will be start it
> > using "java -jar webConfig.jar" without unnecessary actions.
> >
> > As I understand, only Persistence feature requires installation WebConfig
> > on local machine, my be you should create separated project
> > PersistenceGenerator that will use Jetty+H2 and will be packed to single
> > jar.
> >
> > On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <
> akuznetsov@gridgain.com
> > >
> > wrote:
> >
> > > What about docker image?
> > > We will create docker image with installed nodejs, mongo and Ignite Web
> > > Config.
> > > Will this solve this problem?
> > >
> > > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> > dsetrakyan@apache.org>
> > > wrote:
> > >
> > > > From my standpoint, I would like the web-config-download to come as a
> > zip
> > > > file without any extra installation steps if possible.
> > > >
> > > > Ideally, a user should be able to just download it, unzip it, and
> start
> > > > using it.
> > > >
> > > > D.
> > > >
> > > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > > > akuznetsov@gridgain.com>
> > > > wrote:
> > > >
> > > > > Igniters,
> > > > >
> > > > > We are working on Ignite Web Config (ignite-843) and very close to
> > > first
> > > > > version of it.
> > > > > As usual everything could be launched from sources, but for
> usability
> > > > issue
> > > > > I'm thinking
> > > > > about a kind of installer for web config.
> > > > >
> > > > > In web config we are using: nodejs, mongodb, angular.
> > > > >
> > > > > Does any one has experience of packaging web applications for later
> > > > > deployment?
> > > > >
> > > > > Any ideas are very appreciated.
> > > > >
> > > > > --
> > > > > Alexey Kuznetsov
> > > > > GridGain Systems
> > > > > www.gridgain.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: Web config download
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
Sergey,
1. How many connections Jetty + H2 could handle?
Do you have any experience?
2. What is the best way to store JSON into db and later read JSON from db?
3. Persistence feature could not be separated, because CacheTypeMetadata is
a part of CacheConfiguration.
Dmitriy,
What do you think about dropping nodejs and mongoDB in favor of jetty+h2 ?
One more benefit of using java that we could reuse code from Ignite Schema
Import
for connecting to database (using JDBC) and reuse code that generates XML
and POJO classes.
Also we could build and package Web Config with Maven I think.
Actually we do not have much code at server side. So we could switch in a
couple of days I think.
Thoughts?
On Tue, Jun 30, 2015 at 6:25 PM, Sergey Evdokimov <se...@gridgain.com>
wrote:
> I doubt that people will install docker to run WebConfig.
>
> If we expect running WebConfig on user machine node.js + mongoDB is a bad
> choose. Most of our users are java developers, the plain way is to use
> Jetty + H2 and pack whole WebConfig to single jar. User will be start it
> using "java -jar webConfig.jar" without unnecessary actions.
>
> As I understand, only Persistence feature requires installation WebConfig
> on local machine, my be you should create separated project
> PersistenceGenerator that will use Jetty+H2 and will be packed to single
> jar.
>
> On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <akuznetsov@gridgain.com
> >
> wrote:
>
> > What about docker image?
> > We will create docker image with installed nodejs, mongo and Ignite Web
> > Config.
> > Will this solve this problem?
> >
> > On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org>
> > wrote:
> >
> > > From my standpoint, I would like the web-config-download to come as a
> zip
> > > file without any extra installation steps if possible.
> > >
> > > Ideally, a user should be able to just download it, unzip it, and start
> > > using it.
> > >
> > > D.
> > >
> > > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > > akuznetsov@gridgain.com>
> > > wrote:
> > >
> > > > Igniters,
> > > >
> > > > We are working on Ignite Web Config (ignite-843) and very close to
> > first
> > > > version of it.
> > > > As usual everything could be launched from sources, but for usability
> > > issue
> > > > I'm thinking
> > > > about a kind of installer for web config.
> > > >
> > > > In web config we are using: nodejs, mongodb, angular.
> > > >
> > > > Does any one has experience of packaging web applications for later
> > > > deployment?
> > > >
> > > > Any ideas are very appreciated.
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > > GridGain Systems
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Web config download
Posted by Sergey Evdokimov <se...@gridgain.com>.
I doubt that people will install docker to run WebConfig.
If we expect running WebConfig on user machine node.js + mongoDB is a bad
choose. Most of our users are java developers, the plain way is to use
Jetty + H2 and pack whole WebConfig to single jar. User will be start it
using "java -jar webConfig.jar" without unnecessary actions.
As I understand, only Persistence feature requires installation WebConfig
on local machine, my be you should create separated project
PersistenceGenerator that will use Jetty+H2 and will be packed to single
jar.
On Tue, Jun 30, 2015 at 1:24 PM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> What about docker image?
> We will create docker image with installed nodejs, mongo and Ignite Web
> Config.
> Will this solve this problem?
>
> On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <ds...@apache.org>
> wrote:
>
> > From my standpoint, I would like the web-config-download to come as a zip
> > file without any extra installation steps if possible.
> >
> > Ideally, a user should be able to just download it, unzip it, and start
> > using it.
> >
> > D.
> >
> > On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> > akuznetsov@gridgain.com>
> > wrote:
> >
> > > Igniters,
> > >
> > > We are working on Ignite Web Config (ignite-843) and very close to
> first
> > > version of it.
> > > As usual everything could be launched from sources, but for usability
> > issue
> > > I'm thinking
> > > about a kind of installer for web config.
> > >
> > > In web config we are using: nodejs, mongodb, angular.
> > >
> > > Does any one has experience of packaging web applications for later
> > > deployment?
> > >
> > > Any ideas are very appreciated.
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Re: Web config download
Posted by Alexey Kuznetsov <ak...@gridgain.com>.
What about docker image?
We will create docker image with installed nodejs, mongo and Ignite Web
Config.
Will this solve this problem?
On Mon, Jun 29, 2015 at 4:07 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> From my standpoint, I would like the web-config-download to come as a zip
> file without any extra installation steps if possible.
>
> Ideally, a user should be able to just download it, unzip it, and start
> using it.
>
> D.
>
> On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <
> akuznetsov@gridgain.com>
> wrote:
>
> > Igniters,
> >
> > We are working on Ignite Web Config (ignite-843) and very close to first
> > version of it.
> > As usual everything could be launched from sources, but for usability
> issue
> > I'm thinking
> > about a kind of installer for web config.
> >
> > In web config we are using: nodejs, mongodb, angular.
> >
> > Does any one has experience of packaging web applications for later
> > deployment?
> >
> > Any ideas are very appreciated.
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Web config download
Posted by Dmitriy Setrakyan <ds...@apache.org>.
>From my standpoint, I would like the web-config-download to come as a zip
file without any extra installation steps if possible.
Ideally, a user should be able to just download it, unzip it, and start
using it.
D.
On Mon, Jun 29, 2015 at 12:33 AM, Alexey Kuznetsov <ak...@gridgain.com>
wrote:
> Igniters,
>
> We are working on Ignite Web Config (ignite-843) and very close to first
> version of it.
> As usual everything could be launched from sources, but for usability issue
> I'm thinking
> about a kind of installer for web config.
>
> In web config we are using: nodejs, mongodb, angular.
>
> Does any one has experience of packaging web applications for later
> deployment?
>
> Any ideas are very appreciated.
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>