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 our testing and deployment to make use of the flexibility of the Cloud and AWS. This concludes this book.
Implementing Cloud Design Patterns for AWS
Implementing Cloud Design Patterns for AWS
Overview of this book
Table of Contents (18 chapters)
Implementing Cloud Design Patterns for AWS
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
Introduction
Basic Patterns
Patterns for High Availability
Patterns for Processing Static Data
Patterns for Processing Dynamic Data
Patterns for Uploading Data
Patterns for Databases
Patterns for Data Processing
Patterns for Operation and Maintenance
Patterns for Networking
Throw-away Environments
Index
Customer Reviews