Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Implementing Cloud Design Patterns for AWS

You're reading from   Implementing Cloud Design Patterns for AWS Solutions and design ideas for solving system design problems

Arrow left icon
Product type Paperback
Published in Apr 2019
Publisher Packt
ISBN-13 9781789136203
Length 274 pages
Edition 2nd Edition
Tools
Arrow right icon
Authors (4):
Arrow left icon
Clive Harber Clive Harber
Author Profile Icon Clive Harber
Clive Harber
Sean Keery Sean Keery
Author Profile Icon Sean Keery
Sean Keery
Rick Farmer Rick Farmer
Author Profile Icon Rick Farmer
Rick Farmer
Marcus Young Marcus Young
Author Profile Icon Marcus Young
Marcus Young
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Section 1: The Basics
2. Introduction to Amazon Web Services FREE CHAPTER 3. Core Services - Building Blocks for Your Product 4. Availability Patterns - Understanding Your Needs 5. Security - Ensuring the Integrity of Your Systems 6. Section 2: DevOps Patterns
7. Continuous Deployment - Introducing New Features with Minimal Risk 8. Ephemeral Environments - Sandboxes for Experiments 9. Operation and Maintenance - Keeping Things Running at Peak Performance 10. Application Virtualization - Using Cloud Native Patterns for Your Workloads 11. Antipatterns - Avoiding Counterproductive Solutions 12. Section 3: Persistence Patterns
13. Databases - Identifying Which Type Fits Your Needs 14. Data Processing - Handling Your Data Transformation 15. Observability - Understanding How Your Products Are Behaving 16. Anti-Patterns - Bypassing Inferior Options 17. Other Books You May Enjoy

Exploring deployment strategies

Traditionally, deployment of software was a rare event. Every year, you would take all the new product features, bundle them up, and install them on your servers. The tightly coupled features of your monolith introduced a great deal of risk. If there was a single fault in your code, it could cause cascading failures in your product. Modern cloud development practices recommend decomposing your software. We have followed this pattern by creating separate files for unrelated Terraform resources. Segmenting our content even more would have given us additional benefits, but we are striving for a minimal viable product (optimization will come later). 

In our case, deploying immediately to a production environment could have impacts on our product's service level agreements. Cycling our WordPress instances...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image