"App Engines," also known as "Application Containers," promise to simplify application development and deployment by managing load balancing and horizontal scaling for you. This is often accompanied by some limitations in what your application can do. In exchange for that, you get a stable environment that is kept up-to-date for you, and you are relieved from having to provision and monitor the system. Examples include the Google App Engine, the Yahoo! Application Platform, and AWS Elastic Beanstalk.
Have you used an App Engine in your application? Where did it fit in your application? Did the App Engine provide everything you need, or did you have to go outside the bounds of the Engine to build your complete application? What limitations or issues did you run into using this in production? How do you manage this as part of your infrastructure? War stories about why you couldn't use it are also interesting. Or, do you work on an App Engine? Can you come and tell us about it's capabilities and the kinds of applications (demos would be great) that have been built with it?
I'm looking for speakers for this event. Can you give a 20-25 minute talk on this topic? Please message Chris Westin directly if you would like to present.
This month, we're also going to try starting the evening with a brief lightning talk (5 minutes, 20 slides, 15 seconds/slide) session. I'll allow time for up to 2-3 of these. The lightning talks can be about anything this audience will find interesting--so don't limit yourself to the evening's topic. If you are interested in giving a lightning talk, please message Chris Westin directly.
Comments