Book Image

Python Microservices Development

Book Image

Python Microservices Development

Overview of this book

We often deploy our web applications into the cloud, and our code needs to interact with many third-party services. An efficient way to build applications to do this is through microservices architecture. But, in practice, it's hard to get this right due to the complexity of all the pieces interacting with each other. This book will teach you how to overcome these issues and 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: you’ll build everything using Python 3 and its amazing tooling ecosystem. You will understand the principles of TDD and apply them. You will use Flask, Tox, and other tools to build your services using best practices. You will learn how to secure connections between services, and how to script Nginx using Lua to build web application firewall features such as rate limiting. You will also familiarize yourself with Docker’s role in microservices, and use Docker containers, CoreOS, and Amazon Web Services to deploy your services. This book will take you on a journey, ending with the creation of a complete Python application based on microservices. By the end of the book, you will be well versed with the fundamentals of building, designing, testing, and deploying your Python microservices.
Table of Contents (20 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Introduction

Monolithic design


This section presents extracts from the source code of the monolithic version of Runnerly. The whole application can be found at https://github.com/Runnerly/monolith, if you want to study it in detail.

A design pattern that is often referred to when building applications is the Model-View-Controller (MVC), which separates the code into three parts:

  • Model: This manages the data
  • View: This displays the Model for a particular context (web view, PDF view, and so on)
  • Controller: This manipulates the Model to change its state

While it's clear that SQLAlchemy can be the Model part, the View and Controller distinction can be a bit vague when it comes to Flask because what is called a view is a function that receives a request and sends back a response. And that function can both display and manipulate the data. So it can act as a View and as a Controller.

The Django project uses the Model-View-Template (MVT) acronym to describe that pattern, where View is the Python callable, and Template...