How to organize work with a third-party database in Django?

Question

Django

Good day.
I wondered if there is a Django project and a third-party database that is responsible for the operation of the game server. Periodically, data may be received from Django, which will be transferred to the game server and stored there in the database.
What are the options for organizing communication between them? There is an idea to use something as a broker, but the whole problem is that the two projects are completely separate, the database and its structure can change at any time, and opening a bunch of connections to the database is also not a good option.
Perhaps someone has come across a similar puzzle, please share your architectural solutions.

Answer 1

Dzhanga knows how to handle separate
databases Dzhanga knows how to map to an existing table in a database

Answer 2

Just because the projects are different and can change their internal structure, the broker option seems to be a good one. True, writing data from Dzhangi directly to the game server database is not very correct, it is better to make some kind of handler there that will listen to the queue and write to this database.