You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by César Camilo Lugo Marcos <ce...@sisorg.com.mx> on 2016/08/26 17:47:10 UTC
Isis in cloud services
Hello,
I just wanted to let you know that we have been testing our application
in tree cloud services so far, with good results in two of them:
Amazon Web Services Elastic Beanstalk. Working fine, volume load testing
automatically scales instances up and down just.
Heroku. Working fine, volume load testing automatically scales Dynos up
and down just fine.
Google App Engine, works fine in development mode, but when you deploy
the ISIS app does not start. It looks like this is due to the fact that
Apache Wicket uses some non scalable features of Java, and Google blocks
those features of Java. Another issue is that Google App Engine only
supports Java 1.7 and not 1.8 .
We are using PostgreSQL in all cases.
Cesar.
Re: Isis in cloud services
Posted by César Camilo Lugo Marcos <ce...@sisorg.com.mx>.
Hello Martin,
of course your assistance and recommendations, as well as Dan's guidance
have been quite valuable. Thank you for pointing out about Heroku. Yes
we use Wicket viewer, and so far it works fine. After your kind and
valuable recommendations here, I think we might want to make some more
extensive tests on Heroku.
I think I sent earlier the issues we faced with Google Cloud, not on the
top oof my mind right now, but will try to find the email and forward it
to you. Anyway, because of Java issues and Datanucleous issues I don't
think we will go that way.
Cesar.
On Fri, 2016-08-26 at 20:52 +0200, Martin Grigorov wrote:
> Hi Cesar,
>
> Thanks for sharing this information with us!
>
> On Fri, Aug 26, 2016 at 7:47 PM, César Camilo Lugo Marcos <
> cesar.lugo@sisorg.com.mx> wrote:
>
> > Hello,
> >
> > I just wanted to let you know that we have been testing our application
> > in tree cloud services so far, with good results in two of them:
> >
> > Amazon Web Services Elastic Beanstalk. Working fine, volume load testing
> > automatically scales instances up and down just.
> >
> > Heroku. Working fine, volume load testing automatically scales Dynos up
> > and down just fine.
> >
>
> Did you use the Wicket viewer in the testing ?
> I ask because Heroku is designed for stateless applications and Wicket
> applications very quickly become stateful if the developer doesn't pay
> special attention. Isis Wicket viewer is definitely stateful.
> For stateful apps you either need sticky sessions or distributed session
> storage. AFAIK Heroku doesn't support sticky sessions.
>
>
> >
> > Google App Engine, works fine in development mode, but when you deploy
> > the ISIS app does not start. It looks like this is due to the fact that
> > Apache Wicket uses some non scalable features of Java, and Google blocks
> >
>
> Can you please share more details about the issues you faced here ?
> There are some basic configuration settings one has to make to be able to
> run at GAE (
> https://github.com/wicketstuff/core/blob/b1f603b147e5899528f40af65d2e033d166c340a/gae-initializer-parent/gae-initializer/src/main/java/org/wicketstuff/gae/GaeInitializer.java#L20-L40).
> But maybe there was something more ?!
>
>
> > those features of Java. Another issue is that Google App Engine only
> > supports Java 1.7 and not 1.8 .
> >
>
> Yes, and old versions of Jetty and DataNucleus...
>
>
> >
> > We are using PostgreSQL in all cases.
> >
> > Cesar.
> >
> >
Re: Isis in cloud services
Posted by César Camilo Lugo Marcos <ce...@sisorg.com.mx>.
BTW, we did not try MS Azure because for managed services the only
database they support is SQL Azure (MS SQL Server engine). Yes you can
provide your own database, but it will not manage it. Naaaah. :D
On Fri, 2016-08-26 at 20:52 +0200, Martin Grigorov wrote:
> Hi Cesar,
>
> Thanks for sharing this information with us!
>
> On Fri, Aug 26, 2016 at 7:47 PM, César Camilo Lugo Marcos <
> cesar.lugo@sisorg.com.mx> wrote:
>
> > Hello,
> >
> > I just wanted to let you know that we have been testing our application
> > in tree cloud services so far, with good results in two of them:
> >
> > Amazon Web Services Elastic Beanstalk. Working fine, volume load testing
> > automatically scales instances up and down just.
> >
> > Heroku. Working fine, volume load testing automatically scales Dynos up
> > and down just fine.
> >
>
> Did you use the Wicket viewer in the testing ?
> I ask because Heroku is designed for stateless applications and Wicket
> applications very quickly become stateful if the developer doesn't pay
> special attention. Isis Wicket viewer is definitely stateful.
> For stateful apps you either need sticky sessions or distributed session
> storage. AFAIK Heroku doesn't support sticky sessions.
>
>
> >
> > Google App Engine, works fine in development mode, but when you deploy
> > the ISIS app does not start. It looks like this is due to the fact that
> > Apache Wicket uses some non scalable features of Java, and Google blocks
> >
>
> Can you please share more details about the issues you faced here ?
> There are some basic configuration settings one has to make to be able to
> run at GAE (
> https://github.com/wicketstuff/core/blob/b1f603b147e5899528f40af65d2e033d166c340a/gae-initializer-parent/gae-initializer/src/main/java/org/wicketstuff/gae/GaeInitializer.java#L20-L40).
> But maybe there was something more ?!
>
>
> > those features of Java. Another issue is that Google App Engine only
> > supports Java 1.7 and not 1.8 .
> >
>
> Yes, and old versions of Jetty and DataNucleus...
>
>
> >
> > We are using PostgreSQL in all cases.
> >
> > Cesar.
> >
> >
Re: Isis in cloud services
Posted by Martin Grigorov <mg...@apache.org>.
Hi Cesar,
Thanks for sharing this information with us!
On Fri, Aug 26, 2016 at 7:47 PM, César Camilo Lugo Marcos <
cesar.lugo@sisorg.com.mx> wrote:
> Hello,
>
> I just wanted to let you know that we have been testing our application
> in tree cloud services so far, with good results in two of them:
>
> Amazon Web Services Elastic Beanstalk. Working fine, volume load testing
> automatically scales instances up and down just.
>
> Heroku. Working fine, volume load testing automatically scales Dynos up
> and down just fine.
>
Did you use the Wicket viewer in the testing ?
I ask because Heroku is designed for stateless applications and Wicket
applications very quickly become stateful if the developer doesn't pay
special attention. Isis Wicket viewer is definitely stateful.
For stateful apps you either need sticky sessions or distributed session
storage. AFAIK Heroku doesn't support sticky sessions.
>
> Google App Engine, works fine in development mode, but when you deploy
> the ISIS app does not start. It looks like this is due to the fact that
> Apache Wicket uses some non scalable features of Java, and Google blocks
>
Can you please share more details about the issues you faced here ?
There are some basic configuration settings one has to make to be able to
run at GAE (
https://github.com/wicketstuff/core/blob/b1f603b147e5899528f40af65d2e033d166c340a/gae-initializer-parent/gae-initializer/src/main/java/org/wicketstuff/gae/GaeInitializer.java#L20-L40).
But maybe there was something more ?!
> those features of Java. Another issue is that Google App Engine only
> supports Java 1.7 and not 1.8 .
>
Yes, and old versions of Jetty and DataNucleus...
>
> We are using PostgreSQL in all cases.
>
> Cesar.
>
>