Hi Cesar, Thanks for sharing this information with us!
On Fri, Aug 26, 2016 at 7:47 PM, César Camilo Lugo Marcos < cesar.l...@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. > >
