Gain insights into clean architecture using Python. Delve into layered systems, design efficient applications, and integrate web components, error handling, and databases with test-driven development practices.

tarball.tar.gz

POSTGRES_USER

POSTGRES_PASSWORD

POSTGRES_HOSTNAME

APPLICATION_DB

POSTGRES_PORT

POSTGRES_DB

Python Execution

Flask

Flask + Postgres

Python Test

Clean architecture is a software design methodology that separates the processes of an application into discrete steps instead of presenting them as “spaghetti code.” With the versatility of Python, software engineers can build performant, modular applications quickly using the Flask framework.

This course will help you build better applications using the principles of clean architecture. You’ll start with an introduction to data flow in clean systems and learn about the advantages of layered architectures. Next, you’ll learn system components and the connections between application layers. You’ll then design and build a clean system using Python by layering components in guided coding exercises. Finally, you’ll learn how to add functional components for the web, handle errors, and work with external databases using both Postgres and MongoDB. At each step, you’ll use test-driven development practices to ensure robust functionality.

Clean Architecture in Python

Conventional programming can sometimes make our code difficult to understand. This is why professionals are increasingly moving toward layered architecture. Before delving deeper into the details of clean architecture, let’s first discuss the advantages of layered architecture.

# Loosely coupled

The stages of the layered architecture are separated, and there is a great deal of data transformation between these stages. One way we can achieve independence—or loose coupling—between the components of a computer system is through the use of common data formats.

To better understand what loose coupling means for a programmer, let’s consider the last 
#concept=picture#picture#concept# we saw in the previous section. What changes if the web framework was instead a command-line interface (CLI)? 

Let’s learn why a layered architecture is preferred over conventional programming.

Get Started

A Day in the Life of a Clean System

Components of Clean Architecture

A Simple Coding Example

Add a Web Application

Error Management

Integration with a Real External System Postgres

Integration with a Real External System MongoDB

Run a Production-ready System

Appendix

Advantages of a Layered Architecture

Loosely coupled