Book Image

Effective DevOps with AWS - Second Edition

By : Yogesh Raheja, Giuseppe Borgese, Nathaniel Felsen
Book Image

Effective DevOps with AWS - Second Edition

By: Yogesh Raheja, Giuseppe Borgese, Nathaniel Felsen

Overview of this book

The DevOps movement has transformed the way modern tech companies work. Amazon Web Services (AWS), which has been at the forefront of the cloud computing revolution, has also been a key contributor to the DevOps movement, creating a huge range of managed services that help you implement DevOps principles. Effective DevOps with AWS, Second Edition will help you to understand how the most successful tech start-ups launch and scale their services on AWS, and will teach you how you can do the same. This book explains how to treat infrastructure as code, meaning you can bring resources online and offline as easily as you control your software. You will also build a continuous integration and continuous deployment pipeline to keep your app up to date. Once you have gotten to grips will all this, we'll move on to how to scale your applications to offer maximum performance to users even when traffic spikes, by using the latest technologies, such as containers. In addition to this, you'll get insights into monitoring and alerting, so you can make sure your users have the best experience when using your service. In the concluding chapters, we'll cover inbuilt AWS tools such as CodeDeploy and CloudFormation, which are used by many AWS administrators to perform DevOps. By the end of this book, you'll have learned how to ensure the security of your platform and data, using the latest and most prominent AWS tools.
Table of Contents (15 chapters)
Title Page
Packt Upsell

Chapter 6: Scaling Your Infrastructure

  1. No, it is not always the best choice because a multi-level application means more components to manage. If your application works well as a monolith, you can accept a short period of downtime and the traffic will not increase over time. You can also consider letting it run as it is.
  2. In the multi-level approach used in this book, all software is in one ZIP file, instead in a microservices and more in the serverless approach it is broken in multiple parts. For example, in an e-commerce software (the software used to show the content to the users in one service), the part to manage the backend to place a new product is in one service, while the part to manage the payment is in another service, and so on. 
  3. If you are not familiar with the service, it can be difficult. However, AWS is full of documentation and video. Furthermore, in this book we demonstrated how to use a set of basic services to break the classic monolith approach in multi-level.
  4. This is true for an NLB but you need to pre-warm it if you use an ALB or a CLB. You must also do this if your traffic goes up to more than 50 percent every five minutes. 
  5. Using the Certificate Manager is free unless you want to Request a private certificate, a classic SSL * certificate can also cost 500 dollars a year.  
  6. Each AWS Region is organized in AZs and each zone is a separate datacenter. Consequently, it is rare that there are issues in one zone but it is not likely multiple issues in the same moment. Each subnet can belong to only one zone so it is convenient to place each component in at least two, or preferably three, zones.