Book Image

Hands-On Enterprise Application Development with Python

By : Saurabh Badhwar
Book Image

Hands-On Enterprise Application Development with Python

By: Saurabh Badhwar

Overview of this book

Dynamically typed languages like Python are continuously improving. With the addition of exciting new features and a wide selection of modern libraries and frameworks, Python has emerged as an ideal language for developing enterprise applications. Hands-On Enterprise Application Development with Python will show you how to build effective applications that are stable, secure, and easily scalable. The book is a detailed guide to building an end-to-end enterprise-grade application in Python. You will learn how to effectively implement Python features and design patterns that will positively impact your application lifecycle. The book also covers advanced concurrency techniques that will help you build a RESTful application with an optimized frontend. Given that security and stability are the foundation for an enterprise application, you’ll be trained on effective testing, performance analysis, and security practices, and understand how to embed them in your codebase during the initial phase. You’ll also be guided in how to move on from a monolithic architecture to one that is service oriented, leveraging microservices and serverless deployment techniques. By the end of the book, you will have become proficient at building efficient enterprise applications in Python.
Table of Contents (24 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Testing in the microservices world


As we move away from the Monolithic architecture, we need to understand that the processes that used to work for us in the Monolithic application development also need to move along. During the development of the Monolithic application, we used to work with the testing strategies such as unit testing, which aimed to cover the functionality of the individual methods inside an application, followed by integration testing, which is used to cover the fact that these methods operate correctly with each other.

Inside the microservices architecture, things get a little bit complicated. We now have small services where each service is supposed to perform a specific functionality. These services indeed need to interact with each other over the network to produce any meaningful output for the business use case that might be there. But things do not end here. Each of these microservices are composed of several individual methods and interfaces that it needs to work...