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

The Python library pytest supports the labeling of tests. These new labels need to be registered in the ______ file.

The Python library pytest supports the labeling of tests. These new labels need to be registered in the ______ file.

A complicated system like PostgreSQL is considered an implementation detail in clean architecture.

A complicated system like PostgreSQL is considered an implementation detail in clean architecture.

Integration tests are conditionally executed because they’re slower than standard unit tests.

Integration tests are conditionally executed because they’re faster than standard unit tests.

Integration tests are not significant and are omitted.

Integration tests are significant and are always executed.

Why do we isolate integration tests?

A repository based on a proper database needs to be filled with data when initialized.

A repository based on a proper database needs to be filled with data when initialized.

What happens when a test is marked with the label `integration`, but the option `--integration` is not present?

What happens when a test is marked with the label <code>integration</code>, but the option <code>--integration</code> is not present?

Take this quiz to check your understanding of integrating PostgreSQL.

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

Quiz