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

## API

#key# API: Application Programming Interface #key#s are of uttermost importance in clean architecture. An API is a fixed collection of entry points (methods or objects). Every layer may be accessed by elements that live in inner layers via an API.

The separation between layers and the contents of each layer are not always fixed and immutable. A well-designed system should be able to cope with a variety of practical issues. When we design an architecture, it’s very important to know _where something is and why, as we’ve mentioned previously_ in this course. This becomes even more important when we bend the rules. Solutions to many problems are not always black-and-white; similarly, many decisions come in shades of gray.

# API

#key# API: Application Programming Interface #key#s are of uttermost importance in clean architecture. An API is a fixed collection of entry points (methods or objects). Every layer may be accessed by elements that live in inner layers via an API.

The separation between layers and the contents of each layer are not always fixed and immutable. A well-designed system should be able to cope with a variety of practical issues. When we design an architecture, it’s very important to know _where something is and why, as we’ve mentioned previously_ in this course. This becomes even more important when we bend the rules. Solutions to many problems are not always black-and-white; similarly, many decisions come in shades of gray.

Let’s learn about the importance of APIs in clean architecture.

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

APIs and Shades of Gray

API