MySQL replication for Graphene Django

[GABAnich]

I'm using Graphene as a GraphQL server in Django.
I set up a MySQL replica in Django. My setting is pretty simple. Read requests -> Replica. Write requests -> Source

Mutations works in the next way: They modify data and then return modified/new data.
Graphene modifies data in Source and immediately selecting them from Replica.
The problem is that updated data is not immediately appearing in Replica DB (because of Replication delay). As result, some mutations simply do not work.

I have a solution - specifying the Django database in every mutation. Didn't tried it yet. But the project is huge, and this requires a lot of changes in the codebase.

I'm looking for simpler solutions.

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'db_name',
        'USER': 'root',
        'HOST': MYSQL_HOST,
        'PORT': '3306',
    },
    'read_replica': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'db_name_replica',
        'USER': 'root',
        'HOST': MYSQL_HOST_REPLICA,
        'PORT': '3306',
    }
}
DATABASE_ROUTERS = ['app.db_router.DatabaseRouter']

class DatabaseRouter:
    def db_for_read(self, model, **hints):
        return 'read_replica'

    def db_for_write(self, model, **hints):
        return 'default'

    def allow_relation(self, obj1, obj2, **hints):
        return True

    def allow_migrate(self, db, app_label, model_name=None, **hints):
        return True

[matt-dalton]

Did you find anything workable here @GABAnich ? I was also thinking directing mutation responses to the write database would be a useful abstraction

[erikwrede]

Moving to Graphene-Django, as this issue doesn’t address any core features of graphene.

[ulgens]

I'm not sure this issue is in the scope of graphene-django either. You can put anything in the place of gql on the schema above. That problem is called "replication lag" and many articles can be found with "Django read replication lag" search.