Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Cloud Native Python

You're reading from   Cloud Native Python Build and deploy resilent applications on the cloud using microservices, AWS, Azure and more

Arrow left icon
Product type Paperback
Published in Jul 2017
Publisher Packt
ISBN-13 9781787129313
Length 374 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Manish Sethi Manish Sethi
Author Profile Icon Manish Sethi
Manish Sethi
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Introducing Cloud Native Architecture and Microservices 2. Building Microservices in Python FREE CHAPTER 3. Building a Web Application in Python 4. Interacting Data Services 5. Building WebViews with React 6. Creating UIs to Scale with Flux 7. Learning Event Sourcing and CQRS 8. Securing the Web Application 9. Continuous Delivery 10. Dockerizing Your Services 11. Deploying on the AWS Platform 12. Implementing on the Azure Platform 13. Monitoring the Cloud Application

Introduction

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...

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 €18.99/month. Cancel anytime