Hi John, On 5 Mar 2015, at 7:13 am, John Huss <[email protected]> wrote:
> You're missing out big time using the traditional deployment model on AWS. > If you instead use an deployment model that includes an elastic load balancer > you get a ton of benefits: > > 1) it automatically replaces dead instances. > 2) it can automatically scale up if needed > 3) lots of free monitoring graphs, etc > 4) highly available = the load balancer never fails (unlike wotaskd and pals) > > For simplicity I recommend using elastic beanstalk and deploying a WAR file. > But you could also build a docker image and deploy a traditional app instead > (using beanstalk), but without the cruft of wotaskd and javamonitor. > > In the long term - the AWS container service is in beta and allows deploying > docker images across a fleet of EC2 instances. This the best model for > deploying WO apps since you typically want to have multiple app processes > running on each machine rather than a single monolithic process (which is > what WAR deployment gives you). Are you doing any of this in practice? How do you handle session persistence? -- Paul Hoadley http://logicsquad.net/
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
