All geek questions in one place

Does anyone run the Wicket app on the Google-App Engine?

We have many Wicket-based applications that end with a standalone Java Tomcat server. We plan to migrate some of them to the Google App Engine. Has anyone tried to run similar applications (Wicket heavy) on GAEJ? Are there any problems with session processing in GAEJ (the documentation indicates that it should work - http://code.google.com/appengine/docs/java/config/appconfig.html#Enabling_Sessions )? Anything else I need to know before jumping into it?

+3
source share
4 answers

one person with a high degree of fatigue, a person very stateless. these two styles do not get along.

in fact, GAE tries to send the same client to the same server and keep memcache content as long as possible. but it’s nothing. an application that requires a large number of states in memory is simply not the best GAE client.

+2
source

Look at the “ Will it play in Google App Engine ” section of the Wicket and you will see that there are some workarounds.

As for the sessions - avoid the plague. All session information is stored in the DataStore Persistence repository and will be slow and will contribute to your quotas.

EDIT: , MemCache, DataStore .

+2

, Google-AppEngine-Initializer, pom github.

, , ajax fallbacklinks eventbus .

+2

, . GAE, .

+1

Source: https://habr.com/ru/post/1757917/

More articles:


All Articles