> support search and paging, etcd cannot support such features. back-end search and paging is unnecessary, we can implement it in the front-end, because users will not have too many configurations.
YuanSheng Wang <[email protected]> 于2020年8月20日周四 上午11:29写道： > On Thu, Aug 20, 2020 at 10:57 AM vincixu <[email protected]> wrote: > > > I haven't followed APISIX Dashboard until I saw this email. > > In my opinion, APISIX Dashboard should not rely on storage other than > ETCD > > or even ManagerAPI, which will increase the overall complexity. > > > > `manager api` relies on relational databases, because some data needs to > support search and paging, etcd cannot support such features. > > For the `route.name` field, it is necessary to ensure that it is unique > among all routes, which cannot be implemented in etcd. > > > > This is really not a good idea. Dashboard should be kept simple and easy > to > > deploy, not another huge application. > > > > Justin Mclean <[email protected]> 于2020年8月20日周四 上午10:05写道： > > > > > HI, > > > > > > Last I looked mysql was also GPL which is not compatible with the > Apache > > > License. I assume this is an optional dependancy? > > > > > > Thanks, > > > Justin > > > > > -- > > *MembPhis* > My GitHub: https://github.com/membphis > Apache APISIX: https://github.com/apache/incubator-apisix >
