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

Test engineering


The role of testers is changing. The key word here is "changing". Automation is eating the software world. Testing has traditionally been a largely manual effort. More often than not, unit testing has been the only testing that is automated and all other testing is performed manually. In this chapter, we will discuss how to reliably extend test automation all the way through end-to-end testing with a technique I call transitive testing. All this automation has the testing community wondering whether or not their jobs will disappear. I think it is fair to say that the traditional role of testers will disappear, but will be replaced with higher value responsibilities.

These new responsibilities do not include writing automated tests. Writing automated tests is a development task. Developers spend years honing their skills. Treating test automation as anything less than code and expecting testers to learn to code overnight is unrealistic. I know plenty of testers who love to...