In this chapter we want to show how you can work with Elastic Beanstalk in your every day —work— life. Developing applications can be facilitated when using Elastic Beanstalk, especially when you work with Eclipse. Your continuous integration testing can be configured to integrate with Elastic Beanstalk as well. Running production environments will use many of the concepts we explored in Chapter 2. We’ll use Elastic Beanstalk Configurations to quickly spin up entire environments for staging or performance testing purposes. And, in the end, we’ll take one of these environments and start looking for limits with serious load tests.
In the most limited life cycle you have one environment: the production environment. But in most cases, you also have at least a development environment. If your audience (or app) grows, you will find the need to include one or two environments to minimize the impact of rolling out features and functionality. Often, an application ends up with four different kinds of environments, each with their peculiarities:
Most of the time the local machine is the development environment of choice. But if you cooperate/collaborate with different (groups of) people, you want to share your work. Especially when you work with multi-disciplinary teams; not everyone has Git and Tomcat running on their laptops.
Before you can do any sort of production deployment, you need to ...