You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Entropy <bl...@gmail.com> on 2016/05/02 16:10:19 UTC
Wicket on the Amazon Cloud?
We've done our last several apps in Wicket. It's our framework. But our
next app, the client has stated they want implemented on Amazon WebServices
Cloud. Because of the automatic scaling, the advice seems to be that you
want to write your apps to be stateless. But of course, Wicket is very
stateful.
So the question here is, has anyone implemented Wicket in AWS Cloud in such
as way as to take advantage of the auto-scaling? Any tips?
--
View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-on-the-Amazon-Cloud-tp4674520.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicket on the Amazon Cloud?
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
+1 to what Edmont Urbani said!
You either need to keep your pages stateless or you need to use distributed
page store (see
https://github.com/wicketstuff/core/tree/master/datastores-parent for
several impls).
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Mon, May 2, 2016 at 5:24 PM, Urbani, Edmund <ed...@lilandit.com>
wrote:
> On 05/02/2016 04:10 PM, Entropy wrote:
>
> We've done our last several apps in Wicket. It's our framework. But our
> next app, the client has stated they want implemented on Amazon WebServices
> Cloud. Because of the automatic scaling, the advice seems to be that you
> want to write your apps to be stateless. But of course, Wicket is very
> stateful.
>
> So the question here is, has anyone implemented Wicket in AWS Cloud in such
> as way as to take advantage of the auto-scaling? Any tips?
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-on-the-Amazon-Cloud-tp4674520.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
> Also, rather than using session replication, you might store sessions in
> Dynamo DB:
>
> http://java.awsblog.com/post/Tx12CFK2FZ7PXRN/Amazon-DynamoDB-Session-Manager-for-Apache-Tomcat
>
> --
>
> Edmund Urbani
> Liland IT Team
>
> Email: <Ed...@lilandit.com>Edmund.Urbani@Lilandit.com
>
> Liland IT GmbH ...does IT better
> Tel: +43 463 220111
> Fax: +43 463 220111-33
> Tel(GER): +49 221 65028588
>
> Find us at Facebook http://facebook.com/Lilandit
> http://green-badges.com
> http://iventcloud.com
> http://Lilandit.com
>
> <http://www.LilandIT.com> <http://www.LilandIT.com>
>
> Copyright © 2016, Liland IT GmbH
>
> Diese Mail enthaelt vertrauliche und/oder rechtlich geschuetzte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese Email irrtuemlich
> erhalten haben, informieren Sie bitte sofort den Absender und vernichten
> Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe
> dieser Mail ist nicht gestattet.
>
> This email may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this email in
> error) please notify the sender immediately and destroy this email. Any
> unauthorised copying, disclosure or distribution of the material in this
> email is strictly forbidden.
>
Re: Wicket on the Amazon Cloud?
Posted by "Urbani, Edmund" <ed...@lilandit.com>.
On 05/02/2016 04:10 PM, Entropy wrote:
> We've done our last several apps in Wicket. It's our framework. But our
> next app, the client has stated they want implemented on Amazon WebServices
> Cloud. Because of the automatic scaling, the advice seems to be that you
> want to write your apps to be stateless. But of course, Wicket is very
> stateful.
>
> So the question here is, has anyone implemented Wicket in AWS Cloud in such
> as way as to take advantage of the auto-scaling? Any tips?
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-on-the-Amazon-Cloud-tp4674520.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
Also, rather than using session replication, you might store sessions in Dynamo DB:
http://java.awsblog.com/post/Tx12CFK2FZ7PXRN/Amazon-DynamoDB-Session-Manager-for-Apache-Tomcat
--
Edmund Urbani
Liland IT Team
Email: Edmund.Urbani@Lilandit.com <ma...@lilandit.com>
Liland IT GmbH ...does IT better
Tel: +43 463 220111
Fax: +43 463 220111-33
Tel(GER): +49 221 65028588
Find us at Facebook http://facebook.com/Lilandit
http://green-badges.com
http://iventcloud.com
http://Lilandit.com
<http://www.LilandIT.com> <http://www.LilandIT.com>
Copyright 2016, Liland IT GmbH
Diese Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Email irrtuemlich erhalten
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.
This email may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this email in error)
please notify the sender immediately and destroy this email. Any unauthorised
copying, disclosure or distribution of the material in this email is strictly
forbidden.
Re: Wicket on the Amazon Cloud?
Posted by "Urbani, Edmund" <ed...@lilandit.com>.
On 05/02/2016 04:10 PM, Entropy wrote:
> We've done our last several apps in Wicket. It's our framework. But our
> next app, the client has stated they want implemented on Amazon WebServices
> Cloud. Because of the automatic scaling, the advice seems to be that you
> want to write your apps to be stateless. But of course, Wicket is very
> stateful.
A typical Wicket application is stateful in order to take full advantage of
Wicket's features, but it does not have to be (see
http://examples7x.wicket.apache.org/stateless/).
>
> So the question here is, has anyone implemented Wicket in AWS Cloud in such
> as way as to take advantage of the auto-scaling? Any tips?
I have not done this with AWS but I assume the issues there are not that much
different from other load-balancing / clustering setups. A crucial decision is
whether to use sticky sessions. Without sticky sessions you will typically need
session replication (again assuming your webapp is stateful) and if you keep
your sessions to a minimal size eg. through loadable-detachable models, this
should work reasonably well.
>
> --
> View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-on-the-Amazon-Cloud-tp4674520.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
--
Edmund Urbani
Liland IT Team
Email: Edmund.Urbani@Lilandit.com <ma...@lilandit.com>
Liland IT GmbH ...does IT better
Tel: +43 463 220111
Fax: +43 463 220111-33
Tel(GER): +49 221 65028588
Find us at Facebook http://facebook.com/Lilandit
http://green-badges.com
http://iventcloud.com
http://Lilandit.com
<http://www.LilandIT.com> <http://www.LilandIT.com>
Copyright 2016, Liland IT GmbH
Diese Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Email irrtuemlich erhalten
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.
This email may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this email in error)
please notify the sender immediately and destroy this email. Any unauthorised
copying, disclosure or distribution of the material in this email is strictly
forbidden.