Fundamentals of DevOps and Software Delivery

Chapter 3. How to Deploy Your Apps

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 3rd chapter of the final book. Please note that the GitHub repo will be made active later on.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

In Chapter 1 and Chapter 2, you deployed an app on a single server. This is a great way to learn and to get started, and for smaller and simpler apps, a single server may be all you ever need. However, for many production use cases, where you’re building a business that depends on that app, you may run into the following problems with just a single server:

Outages due to hardware issues

If the server has a hardware problem, such as the power supply dying, your users will experience an outage until you replace the server.

Outages due to software issues

If the app crashes due to a software problem, such as a bug in the code, your users will experience an outage until you manually restart it.

Outages due to load

If your app becomes popular enough, the load may exceed what a single server can handle, and your users will experience degraded performance, and potentially outages as well.

Outages ...