Right now our thoughts are that we'd like each app to be able to run on it's own EC2 instance if need be, but the databases will all be on one database server.
thanks! On Fri, Jul 17, 2015 at 9:32 AM, Iain Duncan <[email protected]> wrote: > Thanks Jonathan. The inner apps could well be on different machines in the > future, we are intending to design around that if possible. This is an area > I really don't know much about, so any suggestions or pointers at good > resources would be great. Ideally we come up with some scheme where an auth > app handles login and identification, and the inner apps are working only > off some known token somewhere. > > thanks for the help > iain > > On Fri, Jul 17, 2015 at 9:21 AM, Jonathan Vanasco <[email protected]> > wrote: > >> a third option is to use a tween, which would basically be a hybrid of a >> middleware and a sharedlib. >> >> the question I have is on the logistics of deployment -- are these >> different apps going to be on the same machine or will they be on different >> machines? also, how will you coordinate updates and versioning (changes to >> the underlying auth structure could require a redeploy across the board). >> >> -- >> You received this message because you are subscribed to the Google Groups >> "pylons-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/pylons-discuss. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
