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

Continuous Integration


Tox can automate every step you are doing when you change something in your project: running tests on various Python interpreters, verifying coverage and PEP 8 conformance, building documentation, and so on.

But running all the checks on every change can be time and resource consuming, in particular, if you support several interpreters.

A Continuous Integration (CI) system solves this issue by taking care of this work every time something changes in your project.

Pushing your project in a shared repository under a Distributed Version Control System (DVCS) like Git or Mercurial, on a server will let you trigger a CI every time someone pushes a change on the server.

If you work on an open source software, and don't want to maintain your code server, GitHub (http://github.com), GitLab (http://gitlab.com), and Bitbucket (https://bitbucket.org/) are the most popular services. They will host your project for free if it's public, and offer social features, which will make it...