Use an asynchronous command bus and message queues
... just because that's an interesting thing to try.
Update: In !156 (closed), I have a working setup with RabbitMq, but I was still reworking test data creation. But since having to setup/maintain a rabbitmq server on the testing/production environment will probably be a burden, and since I got inspired by fabpot to use PostgreSQL with LISTEN/NOTIFY, I think I will be migrating to PostgreSQL to try that out.
TestTableConfiguration classes I introduced in !156 (closed), are things I want to keep using. So I'll create another ticket for cleaner test table setup.