Book Image

Python Architecture Patterns

By : Jaime Buelta
Book Image

Python Architecture Patterns

By: Jaime Buelta

Overview of this book

Developing large-scale systems that continuously grow in scale and complexity requires a thorough understanding of how software projects should be implemented. Software developers, architects, and technical management teams rely on high-level software design patterns such as microservices architecture, event-driven architecture, and the strategic patterns prescribed by domain-driven design (DDD) to make their work easier. This book covers these proven architecture design patterns with a forward-looking approach to help Python developers manage application complexity—and get the most value out of their test suites. Starting with the initial stages of design, you will learn about the main blocks and mental flow to use at the start of a project. The book covers various architectural patterns like microservices, web services, and event-driven structures and how to choose the one best suited to your project. Establishing a foundation of required concepts, you will progress into development, debugging, and testing to produce high-quality code that is ready for deployment. You will learn about ongoing operations on how to continue the task after the system is deployed to end users, as the software development lifecycle is never finished. By the end of this Python book, you will have developed "architectural thinking": a different way of approaching software design, including making changes to ongoing systems.
Table of Contents (23 chapters)
2
Part I: Design
6
Part II: Architectural Patterns
12
Part III: Implementation
15
Part IV: Ongoing operations
21
Other Books You May Enjoy
22
Index

Test-Driven Development

A very popular technique to approach programming is Test-Driven Development or TDD. TDD consists of putting tests at the center of the developing experience.

This builds on some of the ideas that we exposed earlier in the chapter, though working on them with a more consistent view.

The TDD flow to develop software works as follows:

  1. New functionality is decided on to be added to the code.
  2. A new test is written to define the new functionality. Note that this is done before the code.
  3. The test suite is run to show that it's failing.
  4. The new functionality is then added to the main code, focusing on simplicity. Only the required feature, without extra details, should be added.
  5. The test suite is run to show that the new test is working. This may need to be done several times until the code is ready.
  6. The new functionality is ready! Now the code can be refactored to improve it, avoiding duplication, rearranging elements...