Book Image

Architecting Cloud Native Applications

By : Kamal Arora, Erik Farr, John Gilbert, Piyum Zonooz
Book Image

Architecting Cloud Native Applications

By: Kamal Arora, Erik Farr, John Gilbert, Piyum Zonooz

Overview of this book

Cloud computing has proven to be the most revolutionary IT development since virtualization. Cloud native architectures give you the benefit of more flexibility over legacy systems. This Learning Path teaches you everything you need to know for designing industry-grade cloud applications and efficiently migrating your business to the cloud. It begins by exploring the basic patterns that turn your database inside out to achieve massive scalability. You’ll learn how to develop cloud native architectures using microservices and serverless computing as your design principles. Then, you’ll explore ways to continuously deliver production code by implementing continuous observability in production. In the concluding chapters, you’ll learn about various public cloud architectures ranging from AWS and Azure to the Google Cloud Platform, and understand the future trends and expectations of cloud providers. By the end of this Learning Path, you’ll have learned the techniques to adopt cloud native architectures that meet your business requirements. This Learning Path includes content from the following Packt products: • Cloud Native Development Patterns and Best Practices by John Gilbert • Cloud Native Architectures by Erik Farr et al.
Table of Contents (24 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Encryption


Security in depth is a critical component of cloud-native security. Multiple levels of least privileged access help ensure that access is controlled at each layer of the technology stack. Value-added cloud services, such as CDN, WAF, API gateway, function-as-a-service, and cloud-native databases, take responsibility for many of the non-differentiated aspects of securing cloud-native systems. Drawing the line of the shared responsibility model as high as possible enables teams to focus their core competency on the security of the data layer.

Following our security-by-design practices, teams need to classify the sensitivity level of their domain data. Based on these classifications, teams then design the proper levels of obfuscation into their components. For each request/response payload, for each database table, for each event type, a team must design how data will be obfuscated at the field level.

Data in transit

Coarse-grained encryption of data in transit is necessary when one...