• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: first version of deployment config scripts for Ubuntu/AWS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: first version of deployment config scripts for Ubuntu/AWS


  • Subject: Re: first version of deployment config scripts for Ubuntu/AWS
  • From: Ray Kiddy <email@hidden>
  • Date: Wed, 04 Mar 2015 15:55:14 -0800

On Thu, 05 Mar 2015 08:30:49 +1030
Paul Hoadley <email@hidden> wrote:

> Hi John,
>
> On 5 Mar 2015, at 7:13 am, John Huss <email@hidden> 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:

I am really using AWS here not for its own sake, but as a way to
experiment with Ubuntu deployments, which I use on co-lo servers.

That being said, your observation may be correct.

> > 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)

Well, I am going to assume it is not perfect in all this, but that is
not saying it would not be useful.

Could anyone write about doing this on the wocommunity.org site?

> > 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.

Sounds like this is worth looking at.

> > 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).

I have been looking at Docker. Some of the container management
software is interesting. I suspect that containerization is going to
be most useful for very thin services and WO/EOF apps tend to be ... not
thin. We will see. Containerization might end up being interesting only
in that containers are getting easier to configure, and it might be
much easier to set up our software in containers than on a stand-alone
server.

> Are you doing any of this in practice?  How do you handle session
> persistence?

Well, "in practice" and "able to talk about it" seem to be different
things.... :-)

- ray

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Re: first version of deployment config scripts for Ubuntu/AWS (From: John Huss <email@hidden>)
 >Re: first version of deployment config scripts for Ubuntu/AWS (From: Paul Hoadley <email@hidden>)

  • Prev by Date: Re: first version of deployment config scripts for Ubuntu/AWS
  • Next by Date: fetch limit vs FrontBase
  • Previous by thread: Re: first version of deployment config scripts for Ubuntu/AWS
  • Next by thread: Re: first version of deployment config scripts for Ubuntu/AWS
  • Index(es):
    • Date
    • Thread