前置的 Filter 拦截请求，并根据请求中包含的 IP 和 port 信息计算其所属的 Distro 责任节点， 并将该请求转发到所属的 Distro 责任节点上。  责任节点上的 Controller 将写请求进行解析。  Distro 协议定期执行 Sync 任务，将本机所负责的所有的实例信息同步到其他节点上。 读操作 由于每台机器上都存放了全量数据，因此在每⼀次读操作中，Distro 级别。namespace+group。或者 namespace 级 别。 授权 resource 组成 acs:config:region:namespace:group acs: access controller system 缩写 config：产品名或者模块名 region：区域 namespace：命名空间 group：分组 不同级别授权资源组成 授权⼀个命名空间下所有数据权限 登录 目前采用 spring-security 框 架不能做到这个特殊逻辑控制 console 接口全部代理 控制台这层要走 filter 的服 务，未来都要走 console 的 controller 转发⼀下，以便统 ⼀处理 改这个成本比价高 console 接口部分代理（推荐） 只把配置列表 服务列表 这种高频先整个控制台管控 这是折中方案，未来要走全部 代理方案，以便可分可合

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Controller endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the code and for Spring that the class plays a specific role. In this case, our class is a web @Controller, so Spring considers it when handling incoming web requests. The @RequestMapping annotation provides without any arguments. All of your application components ( @Component, @Service, @Repository, @Controller etc.) are automatically registered as Spring Beans. The following example shows a @Service Bean

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Controller endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the code and for Spring that the class plays a specific role. In this case, our class is a web @Controller, so Spring considers it when handling incoming web requests. The @RequestMapping annotation provides without any arguments. All of your application components ( @Component, @Service, @Repository, @Controller etc.) are automatically registered as Spring Beans. The following example shows a @Service Bean

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Controller endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the code and for Spring that the class plays a specific role. In this case, our class is a web @Controller, so Spring considers it when handling incoming web requests. The @RequestMapping annotation provides without any arguments. All of your application components ( @Component, @Service, @Repository, @Controller etc.) are automatically registered as Spring Beans. The following example shows a @Service Bean

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Controller endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the code and for Spring that the class plays a specific role. In this case, our class is a web @Controller, so Spring considers it when handling incoming web requests. The @RequestMapping annotation provides without any arguments. All of your application components ( @Component, @Service, @Repository, @Controller etc.) are automatically registered as Spring Beans. The following example shows a @Service Bean

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Controller endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the code and for Spring that the class plays a specific role. In this case, our class is a web @Controller, so Spring considers it when handling incoming web requests. The @RequestMapping annotation provides without any arguments. All of your application components ( @Component, @Service, @Repository, @Controller etc.) are automatically registered as Spring Beans. The following example shows a @Service Bean

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Controller endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the code and for Spring that the class plays a specific role. In this case, our class is a web @Controller, so Spring considers it when handling incoming web requests. The @RequestMapping annotation provides without any arguments. All of your application components ( @Component, @Service, @Repository, @Controller etc.) are automatically registered as Spring Beans. The following example shows a @Service Bean

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Controller endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the code and for Spring that the class plays a specific role. In this case, our class is a web @Controller, so Spring considers it when handling incoming web requests. The @RequestMapping annotation provides without any arguments. All of your application components ( @Component, @Service, @Repository, @Controller etc.) are automatically registered as Spring Beans. The following example shows a @Service Bean

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Controller Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the code and for Spring that the class plays a specific role. In this case, our class is a web @Controller, so Spring considers it when handling incoming web requests. The @RequestMapping annotation provides implicitly includes it. All of your application components (@Component, @Service, @Repository, @Controller etc.) are automatically registered as Spring Beans. The following example shows a @Service Bean

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Controller Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the code and for Spring that the class plays a specific role. In this case, our class is a web @Controller, so Spring considers it when handling incoming web requests. The @RequestMapping annotation provides implicitly includes it. All of your application components (@Component, @Service, @Repository, @Controller etc.) are automatically registered as Spring Beans. The following example shows a @Service Bean