Implementing Cloud Design Patterns for AWS

Summary

In this final chapter, we discussed some high-level topics that are making headlines in the DevOps movement and can heavily improve our work with AWS infrastructure. Firstly, we talked about how to move our infrastructure into a code. This allows us to apply things such as peer review, diffing tools, and so on against pending changes to our infrastructure. Next, we moved to temporary development environments and discussed how tools such as Vagrant allow us to get the final servers much closer to the developers. This can prevent things such as software incompatibilities, miscommunications about migrations, and a slew of other possible errors when it is time to get our code to the consuming clients. Finally, we discussed how we can optimize ...