> 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 <akuznet...@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 <sevdoki...@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 < > akuznet...@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 < > > dsetrak...@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 < > > > > akuznet...@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 >