老师，我们在生产环境的项目比较大，我们通过建造一个DependencyProvider
class DependencyProvider {
  DependencyProvider._();

  static DependencyProvider _sharedInstance;
  static DependencyProvider get sharedInstance {
    return _sharedInstance;
  }
  UserService get userService => UserService.sharedInstance(persistenceService);
}

然后通过在页面中注入页面所需的Service来共享数据
DependencyProvider.sharedInstance.userService

感觉也比较清晰，不知道您怎么评价这种机制？
跟Provider相比的优劣势是什么呢？

谢谢您的回复！

final _counter = Provider.of<CounterModel>(context);
    return Scaffold(
      appBar: AppBar(
        title: Text('DataFlow Page2'),
      ),
      //展示资源中的数据
      body: Consumer<CounterModel>(
        builder: (context, CounterModel counter, _) => Center(
          child: Text('Value: ${counter.counter}')
        )
      ),
      // floatingActionButton: FloatingActionButton(
      // child: TestIcon(),
      // onPressed: _counter.increment,
      // ),
      //用资源更新方法来设置按钮点击回调
      floatingActionButton: Consumer<CounterModel>(
        builder: (context, CounterModel counter, child) => FloatingActionButton(
          onPressed: _counter.increment,
          child: child,
        ),
        child: TestIcon(),
      )
    );

如上代码所示，在测试的时候发现，按钮还是会不断的刷新重建