in the read after write scenario, why not use something like consistency tokens ? and redirect to primary if the secondary detects it has not caught up ?