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
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Cloud Native Architectures

You're reading from   Cloud Native Architectures Design high-availability and cost-effective applications for the cloud

Arrow left icon
Product type Paperback
Published in Aug 2018
Publisher Packt
ISBN-13 9781787280540
Length 358 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (4):
Arrow left icon
Tom Laszewski Tom Laszewski
Author Profile Icon Tom Laszewski
Tom Laszewski
Kamal Arora Kamal Arora
Author Profile Icon Kamal Arora
Kamal Arora
Piyum Zonooz Piyum Zonooz
Author Profile Icon Piyum Zonooz
Piyum Zonooz
Erik Farr Erik Farr
Author Profile Icon Erik Farr
Erik Farr
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Introducing Cloud Native Architecture FREE CHAPTER 2. The Cloud Adoption Journey 3. Cloud Native Application Design 4. How to Choose Technology Stacks 5. Scalable and Available 6. Secure and Reliable 7. Optimizing Cost 8. Cloud Native Operations 9. Amazon Web Services 10. Microsoft Azure 11. Google Cloud Platform 12. What's Next? Cloud Native Application Architecture Trends 13. Other Books You May Enjoy

Always-on architectures


For many years, architects have always had two primary concerns: the availability of a given system and the recoverability of the system (often referred to as disaster recovery). These two concepts exist to address inherent qualities of a system deployed on a limited, on-premise infrastructure. In this on-premise infrastructure, there are a finite number of physical or virtual resources performing very specific functions or supporting a specific application. These applications are built in such a way that it negates the ability to run in a distributed manner across multiple machines. This paradigm means that the overall system has many single points of failure, whether it be a single network interface, a virtual machine or physical server, a virtual disk or volume, and so on.

Given these inherent fault points, architects developed two principle assessments to gauge the efficacy of a system. The systems' ability to remain running and perform its function is known as...

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