Skip to content

Architecture Overview

The project follows Django's standard application structure with clear separation of concerns:

insecure-banking/
├── Dockerfile            # Docker container definition
├── manage.py             # Django management script
├── pyproject.toml        # Project metadata and dependencies
├── docs/                 # Documentation
├── scripts/              # Utility scripts
├── src/                  # Application source code
│   ├── config/           # Django project configuration
│   ├── data/             # Data handling utilities
│   └── web/              # Main web application
└── tests/                # Test suite
    ├── e2e/              # End-to-end tests
    ├── integration/      # Integration tests
    ├── security/         # Security tests
    └── unit/             # Unit tests

Application Layers

Configuration Layer

Located in src/config/, this layer contains Django project configuration:

  • settings.py: Django settings and configuration
  • urls.py: Root URL routing
  • wsgi.py and asgi.py: WSGI/ASGI application entry points
  • middleware.py: Custom middleware components

Data Layer

Located in src/data/, this layer handles data operations:

  • YAML data processing
  • Data serialization and deserialization

Web Application Layer

Located in src/web/, this is the main application layer:

  • models.py: Database models (User, Account, Operation)
  • views.py: View functions handling HTTP requests
  • services.py: Business logic and service functions
  • templates/: HTML templates
  • static/: CSS, JavaScript, and static assets
  • migrations/: Database migration files

Component Interactions

URL Routing

URLs are configured in src/config/urls.py and mapped to view functions in src/web/views.py.

Views

Views handle HTTP requests, process data through services, and return HTTP responses using templates.

Services

The service layer in src/web/services.py contains business logic separated from view logic, including:

  • Authentication operations
  • Account operations
  • Transaction processing

Models

Django ORM models represent database tables:

  • User: User accounts and authentication
  • Account: Bank accounts with balances
  • Operation: Transaction records

Templates

Django templates in src/web/templates/ provide the user interface:

  • Base template with common layout
  • Feature-specific templates for different pages
  • Partial templates for reusable components

Static Files

Static assets in src/web/static/ include:

  • Bootstrap CSS framework
  • Custom CSS for styling
  • JavaScript for interactivity
  • Images and fonts