Book Image

Software Architecture with Python

By : Anand Balachandran Pillai
Book Image

Software Architecture with Python

By: Anand Balachandran Pillai

Overview of this book

This book starts by explaining how Python fits into an application's architecture. As you move along, you will get to grips with architecturally significant demands and how to determine them. Later, you’ll gain a complete understanding of the different architectural quality requirements for building a product that satisfies business needs, such as maintainability/reusability, testability, scalability, performance, usability, and security. You will also use various techniques such as incorporating DevOps, continuous integration, and more to make your application robust. You will discover when and when not to use object orientation in your applications, and design scalable applications. The focus is on building the business logic based on the business process documentation, and understanding which frameworks to use and when to use them. The book also covers some important patterns that should be taken into account while solving design problems, as well as those in relatively new domains such as the Cloud. By the end of this book, you will have understood the ins and outs of Python so that you can make critical design decisions that not just live up to but also surpassyour clients’ expectations.
Table of Contents (18 chapters)
Software Architecture with Python
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Refactoring Code


Now that we have seen how static tools can be used to report a wide range of errors and issues in our Python code, let us do a simple exercise of refactoring our code. We will take our poorly written metric test module as the use case (the first version of it), and perform a few refactoring steps.

Here are the rough guidelines we will follow when doing the refactoring:

  1. Fix complex code first: This will get a lot of code out of the way, as typically, when a complex piece of code is refactored, we end up reducing the number of lines of code. This overall improves the code quality, and reduces code smells. You may be creating new functions or classes here, so it always helps to perform this step first.

  2. Do an analysis of the code now: It is a good idea to run the complexity checkers at this step, and see how the overall complexity of the code—class/module or functions—has been reduced. If not, iterate again.

  3. Fix code smells next: Fix any issue with code smells—class, function...