Book Image

Cloud Native Python

By : Manish Sethi
Book Image

Cloud Native Python

By: Manish Sethi

Overview of this book

Businesses today are evolving so rapidly that having their own infrastructure to support their expansion is not feasible. As a result, they have been resorting to the elasticity of the cloud to provide a platform to build and deploy their highly scalable applications. This book will be the one stop for you to learn all about building cloud-native architectures in Python. It will begin by introducing you to cloud-native architecture and will help break it down for you. Then you’ll learn how to build microservices in Python using REST APIs in an event driven approach and you will build the web layer. Next, you’ll learn about Interacting data services and building Web views with React, after which we will take a detailed look at application security and performance. Then, you’ll also learn how to Dockerize your services. And finally, you’ll learn how to deploy the application on the AWS and Azure platforms. We will end the book by discussing some concepts and techniques around troubleshooting problems that might occur with your applications after you’ve deployed them. This book will teach you how to craft applications that are built as small standard units, using all the proven best practices and avoiding the usual traps. It's a practical book: we're going to build everything using Python 3 and its amazing tooling ecosystem. The book will take you on a journey, the destination of which, is the creation of a complete Python application based on microservices over the cloud platform
Table of Contents (14 chapters)
Creating UIs to Scale with Flux


Let's start with reviewing the n-tier architecture, where we have some clients, a network, a business model, some business logic, some data storage, and so on. This is a basic model, which you will find as part of any architectural design. It looks something like the following diagram:

As you can see in this architecture, we have these different models that come into action:

  • View Model: This is basically for client-side interaction
  • DTO Model: This is for communication between the client and the REST Endpoints
  • Business Model: This is a combination of DAO (Data Access Object) and business service, which interprets the user requests, and communicates with the storage service
  • E-R Model: This defines the relationship between entities (that is, DTO and RDMS/NDMS)

Now that you have some idea about the architecture, let's understand its characteristics, which...