You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apisix.apache.org by wei jin <kv...@apache.org> on 2020/08/20 01:51:58 UTC
[DISCUSS]Modify the manager-api DB from mysql to sqllite
hi, community
Many users have reported that the current apisix-dashboard is a little
troublesome during deployment. One of the problems is that we rely on
mysql. Users need to maintain additional database instances.
I propose to modify mysql to an embedded database such as sqllite.
considerations for using sqllite:
1.Simplify the complexity of manager-api deployment.
2.We still need a relational database to organize the relationship and
minimize the changes caused by database changes.
3.sqllite is a relatively mature database.
Any suggestions on this proposal? Or is there a better recommendation for
an embedded database?
Thanks!
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by Ming Wen <we...@apache.org>.
sqlite is Public Domain[1], which is may be included within Apache
products[2].
So it's better choose a DB which is Apache 2.0 license or a compatible
license.
[1] https://www.sqlite.org/copyright.html
[2]
https://www.apache.org/legal/resolved.html#handling-public-domain-licensed-works
Thanks,
Ming Wen, Apache APISIX & Apache SkyWalking
Twitter: _WenMing
Sheng Wu <wu...@gmail.com> 于2020年8月20日周四 上午11:54写道：
> There are a lot of DB could be chosen, if you like. Many of them are Apache
> 2.0 or a compatible license.
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> vincixu <vi...@apache.org> 于2020年8月20日周四 上午11:42写道：
>
> > > 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 <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
> >
> > > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
> > >
> >
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by Sheng Wu <wu...@gmail.com>.
There are a lot of DB could be chosen, if you like. Many of them are Apache
2.0 or a compatible license.
Sheng Wu 吴晟
Twitter, wusheng1108
vincixu <vi...@apache.org> 于2020年8月20日周四 上午11:42写道：
> > 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 <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
>
> > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
> >
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by Zhiyuan Ju <ju...@apache.org>.
That's fine to do page sorting on the front end if there doesn't have too
many records.
I'm not sure where we should implement some logic out of the manager-api,
such as Authentication.
Best Regards!
@ Zhiyuan Ju <https://www.shaoyaoju.org/>
vincixu <vi...@apache.org> 于2020年8月20日周四 上午11:42写道：
> > 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 <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
>
> > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
> >
>
回复： [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by 指尖旳〃圊舂 ︶ <24...@qq.com>.
When we deploy, we need too much skill
golang mysql nodejs reactjs nginx openresty lua etcd shell
Can we try to make APIs IX easier to use
------------------ 原始邮件 ------------------
发件人: "Ming Wen"<wenming@apache.org>;
发送时间: 2020年8月20日(星期四) 下午5:33
收件人: "dev"<dev@apisix.apache.org>;
主题: Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
That will be great if we can remove RDS.
Thanks,
Ming Wen, Apache APISIX & Apache SkyWalking
Twitter: _WenMing
vincixu <vinci@apache.org> 于2020年8月20日周四 下午4:30写道：
> Relational database is not the only way.k8s implement all features(RBAC,
> ABAC, cascade) we need but no relational databases.
> Keep configuration in two places, it will bring a hard problem: how to
> keep consistency.A problem that engineers have struggled for many years but
> there has been no easy solution until now,I think it’s not worth
> introducing such a problem to implement the mentioned features.
> ( I also have never seen a project using etcd and relational storage at the
> same time to store the same data, )
>
> wei jin <kvn@apache.org> 于2020年8月20日周四 下午4:04写道：
>
> > We need a relational database to do some function extensions to meet some
> > practical needs, such as authority management. But we also hope to keep
> > apisix sufficiently convergent and focus on a high-performance gateway.
> > APISIX should not be affected by external function extensions.
> >
> > vincixu <vinci@apache.org> 于2020年8月20日周四 下午3:53写道：
> >
> > > I don't think a lot of routes is a good practice.
> > > But we can discuss how many routes APISIX plans to support. There is no
> > > pressure on the front-end sorting of records less than 50,000
> records(Our
> > > team way).
> > > If we plan to support large rotes query, paging and so on, we can load
> > the
> > > data into memory, and then simulate query and paging in the backend
> > instead
> > > of depend on another storage (the k8s apiserver way),
> > > if we really need a storage that is easy to query, why not directly use
> > it
> > > as the configuration library of APISIX? Just like tyk did( using mongo
> as
> > > configuration storage).
> > > It is very dangerous and inelegant to keep duplicate configuration even
> > in
> > > different storage media.
> > >
> > > YuanSheng Wang <membphis@apache.org> 于2020年8月20日周四 下午12:30写道：
> > >
> > > > On Thu, Aug 20, 2020 at 11:42 AM vincixu <vinci@apache.org> wrote:
> > > >
> > > > > > 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.
> > > > >
> > > >
> > > > > because users will not have too many configurations
> > > >
> > > > Apache APISIX can support a large number of routes, which is an
> > important
> > > > feature for our users.
> > > >
> > > > Another case:
> > > >
> > > > the `service` or `upstream` object can be bound in `route`, when we
> > need
> > > to
> > > > delete the `service`
> > > > or `upstream` object, we need to confirm there is no route using it.
> if
> > > we
> > > > are using RDS, its easy for
> > > > this case.
> > > >
> > > > If we only use etcd, it is hard to support this case too.
> > > >
> > > >
> > > > >
> > > > > YuanSheng Wang <membphis@apache.org> 于2020年8月20日周四 上午11:29写道：
> > > > >
> > > > > > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vinci@apache.org>
> 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 <justin@classsoftware.com> 于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
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > *MembPhis*
> > > > My GitHub: https://github.com/membphis
> > > > Apache APISIX: https://github.com/apache/incubator-apisix
> > > >
> > >
> >
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by Ming Wen <we...@apache.org>.
created a github milestone for this discuss:
https://github.com/apache/apisix-dashboard/milestone/3
Thanks,
Ming Wen, Apache APISIX & Apache SkyWalking
Twitter: _WenMing
wei jin <kv...@apache.org> 于2020年8月21日周五 上午11:04写道：
> ok, I agree that the data is persisted in etcd, which can indeed avoid a
> lot of unnecessary trouble.
>
> YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 下午11:22写道：
>
> > On Thu, Aug 20, 2020 at 5:33 PM Ming Wen <we...@apache.org> wrote:
> >
> > > That will be great if we can remove RDS.
> > >
> >
> > yes, I love this way too.
> >
> >
> > >
> > > Thanks,
> > > Ming Wen, Apache APISIX & Apache SkyWalking
> > > Twitter: _WenMing
> > >
> > >
> > > vincixu <vi...@apache.org> 于2020年8月20日周四 下午4:30写道：
> > >
> > > > Relational database is not the only way.k8s implement all
> > features(RBAC,
> > > > ABAC, cascade) we need but no relational databases.
> > > > Keep configuration in two places, it will bring a hard problem: how
> to
> > > > keep consistency.A problem that engineers have struggled for many
> years
> > > but
> > > > there has been no easy solution until now,I think it’s not worth
> > > > introducing such a problem to implement the mentioned features.
> > > > ( I also have never seen a project using etcd and relational storage
> at
> > > the
> > > > same time to store the same data, )
> > > >
> > > > wei jin <kv...@apache.org> 于2020年8月20日周四 下午4:04写道：
> > > >
> > > > > We need a relational database to do some function extensions to
> meet
> > > some
> > > > > practical needs, such as authority management. But we also hope to
> > keep
> > > > > apisix sufficiently convergent and focus on a high-performance
> > gateway.
> > > > > APISIX should not be affected by external function extensions.
> > > > >
> > > > > vincixu <vi...@apache.org> 于2020年8月20日周四 下午3:53写道：
> > > > >
> > > > > > I don't think a lot of routes is a good practice.
> > > > > > But we can discuss how many routes APISIX plans to support. There
> > is
> > > no
> > > > > > pressure on the front-end sorting of records less than 50,000
> > > > records(Our
> > > > > > team way).
> > > > > > If we plan to support large rotes query, paging and so on, we
> can
> > > load
> > > > > the
> > > > > > data into memory, and then simulate query and paging in the
> backend
> > > > > instead
> > > > > > of depend on another storage (the k8s apiserver way),
> > > > > > if we really need a storage that is easy to query, why not
> directly
> > > use
> > > > > it
> > > > > > as the configuration library of APISIX? Just like tyk did( using
> > > mongo
> > > > as
> > > > > > configuration storage).
> > > > > > It is very dangerous and inelegant to keep duplicate
> configuration
> > > even
> > > > > in
> > > > > > different storage media.
> > > > > >
> > > > > > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 下午12:30写道：
> > > > > >
> > > > > > > On Thu, Aug 20, 2020 at 11:42 AM vincixu <vi...@apache.org>
> > wrote:
> > > > > > >
> > > > > > > > > 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.
> > > > > > > >
> > > > > > >
> > > > > > > > because users will not have too many configurations
> > > > > > >
> > > > > > > Apache APISIX can support a large number of routes, which is an
> > > > > important
> > > > > > > feature for our users.
> > > > > > >
> > > > > > > Another case:
> > > > > > >
> > > > > > > the `service` or `upstream` object can be bound in `route`,
> when
> > we
> > > > > need
> > > > > > to
> > > > > > > delete the `service`
> > > > > > > or `upstream` object, we need to confirm there is no route
> using
> > > it.
> > > > if
> > > > > > we
> > > > > > > are using RDS, its easy for
> > > > > > > this case.
> > > > > > >
> > > > > > > If we only use etcd, it is hard to support this case too.
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四
> 上午11:29写道：
> > > > > > > >
> > > > > > > > > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vinci@apache.org
> >
> > > > 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 <ju...@classsoftware.com> 于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
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > *MembPhis*
> > > > > > > My GitHub: https://github.com/membphis
> > > > > > > Apache APISIX: https://github.com/apache/incubator-apisix
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> >
> > *MembPhis*
> > My GitHub: https://github.com/membphis
> > Apache APISIX: https://github.com/apache/incubator-apisix
> >
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by wei jin <kv...@apache.org>.
ok, I agree that the data is persisted in etcd, which can indeed avoid a
lot of unnecessary trouble.
YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 下午11:22写道：
> On Thu, Aug 20, 2020 at 5:33 PM Ming Wen <we...@apache.org> wrote:
>
> > That will be great if we can remove RDS.
> >
>
> yes, I love this way too.
>
>
> >
> > Thanks,
> > Ming Wen, Apache APISIX & Apache SkyWalking
> > Twitter: _WenMing
> >
> >
> > vincixu <vi...@apache.org> 于2020年8月20日周四 下午4:30写道：
> >
> > > Relational database is not the only way.k8s implement all
> features(RBAC,
> > > ABAC, cascade) we need but no relational databases.
> > > Keep configuration in two places, it will bring a hard problem: how to
> > > keep consistency.A problem that engineers have struggled for many years
> > but
> > > there has been no easy solution until now,I think it’s not worth
> > > introducing such a problem to implement the mentioned features.
> > > ( I also have never seen a project using etcd and relational storage at
> > the
> > > same time to store the same data, )
> > >
> > > wei jin <kv...@apache.org> 于2020年8月20日周四 下午4:04写道：
> > >
> > > > We need a relational database to do some function extensions to meet
> > some
> > > > practical needs, such as authority management. But we also hope to
> keep
> > > > apisix sufficiently convergent and focus on a high-performance
> gateway.
> > > > APISIX should not be affected by external function extensions.
> > > >
> > > > vincixu <vi...@apache.org> 于2020年8月20日周四 下午3:53写道：
> > > >
> > > > > I don't think a lot of routes is a good practice.
> > > > > But we can discuss how many routes APISIX plans to support. There
> is
> > no
> > > > > pressure on the front-end sorting of records less than 50,000
> > > records(Our
> > > > > team way).
> > > > > If we plan to support large rotes query, paging and so on, we can
> > load
> > > > the
> > > > > data into memory, and then simulate query and paging in the backend
> > > > instead
> > > > > of depend on another storage (the k8s apiserver way),
> > > > > if we really need a storage that is easy to query, why not directly
> > use
> > > > it
> > > > > as the configuration library of APISIX? Just like tyk did( using
> > mongo
> > > as
> > > > > configuration storage).
> > > > > It is very dangerous and inelegant to keep duplicate configuration
> > even
> > > > in
> > > > > different storage media.
> > > > >
> > > > > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 下午12:30写道：
> > > > >
> > > > > > On Thu, Aug 20, 2020 at 11:42 AM vincixu <vi...@apache.org>
> wrote:
> > > > > >
> > > > > > > > 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.
> > > > > > >
> > > > > >
> > > > > > > because users will not have too many configurations
> > > > > >
> > > > > > Apache APISIX can support a large number of routes, which is an
> > > > important
> > > > > > feature for our users.
> > > > > >
> > > > > > Another case:
> > > > > >
> > > > > > the `service` or `upstream` object can be bound in `route`, when
> we
> > > > need
> > > > > to
> > > > > > delete the `service`
> > > > > > or `upstream` object, we need to confirm there is no route using
> > it.
> > > if
> > > > > we
> > > > > > are using RDS, its easy for
> > > > > > this case.
> > > > > >
> > > > > > If we only use etcd, it is hard to support this case too.
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
> > > > > > >
> > > > > > > > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org>
> > > 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 <ju...@classsoftware.com> 于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
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > *MembPhis*
> > > > > > My GitHub: https://github.com/membphis
> > > > > > Apache APISIX: https://github.com/apache/incubator-apisix
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
> --
>
> *MembPhis*
> My GitHub: https://github.com/membphis
> Apache APISIX: https://github.com/apache/incubator-apisix
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by YuanSheng Wang <me...@apache.org>.
On Thu, Aug 20, 2020 at 5:33 PM Ming Wen <we...@apache.org> wrote:
> That will be great if we can remove RDS.
>
yes, I love this way too.
>
> Thanks,
> Ming Wen, Apache APISIX & Apache SkyWalking
> Twitter: _WenMing
>
>
> vincixu <vi...@apache.org> 于2020年8月20日周四 下午4:30写道：
>
> > Relational database is not the only way.k8s implement all features(RBAC,
> > ABAC, cascade) we need but no relational databases.
> > Keep configuration in two places, it will bring a hard problem: how to
> > keep consistency.A problem that engineers have struggled for many years
> but
> > there has been no easy solution until now,I think it’s not worth
> > introducing such a problem to implement the mentioned features.
> > ( I also have never seen a project using etcd and relational storage at
> the
> > same time to store the same data, )
> >
> > wei jin <kv...@apache.org> 于2020年8月20日周四 下午4:04写道：
> >
> > > We need a relational database to do some function extensions to meet
> some
> > > practical needs, such as authority management. But we also hope to keep
> > > apisix sufficiently convergent and focus on a high-performance gateway.
> > > APISIX should not be affected by external function extensions.
> > >
> > > vincixu <vi...@apache.org> 于2020年8月20日周四 下午3:53写道：
> > >
> > > > I don't think a lot of routes is a good practice.
> > > > But we can discuss how many routes APISIX plans to support. There is
> no
> > > > pressure on the front-end sorting of records less than 50,000
> > records(Our
> > > > team way).
> > > > If we plan to support large rotes query, paging and so on, we can
> load
> > > the
> > > > data into memory, and then simulate query and paging in the backend
> > > instead
> > > > of depend on another storage (the k8s apiserver way),
> > > > if we really need a storage that is easy to query, why not directly
> use
> > > it
> > > > as the configuration library of APISIX? Just like tyk did( using
> mongo
> > as
> > > > configuration storage).
> > > > It is very dangerous and inelegant to keep duplicate configuration
> even
> > > in
> > > > different storage media.
> > > >
> > > > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 下午12:30写道：
> > > >
> > > > > On Thu, Aug 20, 2020 at 11:42 AM vincixu <vi...@apache.org> wrote:
> > > > >
> > > > > > > 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.
> > > > > >
> > > > >
> > > > > > because users will not have too many configurations
> > > > >
> > > > > Apache APISIX can support a large number of routes, which is an
> > > important
> > > > > feature for our users.
> > > > >
> > > > > Another case:
> > > > >
> > > > > the `service` or `upstream` object can be bound in `route`, when we
> > > need
> > > > to
> > > > > delete the `service`
> > > > > or `upstream` object, we need to confirm there is no route using
> it.
> > if
> > > > we
> > > > > are using RDS, its easy for
> > > > > this case.
> > > > >
> > > > > If we only use etcd, it is hard to support this case too.
> > > > >
> > > > >
> > > > > >
> > > > > > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
> > > > > >
> > > > > > > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org>
> > 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 <ju...@classsoftware.com> 于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
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > *MembPhis*
> > > > > My GitHub: https://github.com/membphis
> > > > > Apache APISIX: https://github.com/apache/incubator-apisix
> > > > >
> > > >
> > >
> >
>
--
*MembPhis*
My GitHub: https://github.com/membphis
Apache APISIX: https://github.com/apache/incubator-apisix
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by Ming Wen <we...@apache.org>.
That will be great if we can remove RDS.
Thanks,
Ming Wen, Apache APISIX & Apache SkyWalking
Twitter: _WenMing
vincixu <vi...@apache.org> 于2020年8月20日周四 下午4:30写道：
> Relational database is not the only way.k8s implement all features(RBAC,
> ABAC, cascade) we need but no relational databases.
> Keep configuration in two places, it will bring a hard problem: how to
> keep consistency.A problem that engineers have struggled for many years but
> there has been no easy solution until now,I think it’s not worth
> introducing such a problem to implement the mentioned features.
> ( I also have never seen a project using etcd and relational storage at the
> same time to store the same data, )
>
> wei jin <kv...@apache.org> 于2020年8月20日周四 下午4:04写道：
>
> > We need a relational database to do some function extensions to meet some
> > practical needs, such as authority management. But we also hope to keep
> > apisix sufficiently convergent and focus on a high-performance gateway.
> > APISIX should not be affected by external function extensions.
> >
> > vincixu <vi...@apache.org> 于2020年8月20日周四 下午3:53写道：
> >
> > > I don't think a lot of routes is a good practice.
> > > But we can discuss how many routes APISIX plans to support. There is no
> > > pressure on the front-end sorting of records less than 50,000
> records(Our
> > > team way).
> > > If we plan to support large rotes query, paging and so on, we can load
> > the
> > > data into memory, and then simulate query and paging in the backend
> > instead
> > > of depend on another storage (the k8s apiserver way),
> > > if we really need a storage that is easy to query, why not directly use
> > it
> > > as the configuration library of APISIX? Just like tyk did( using mongo
> as
> > > configuration storage).
> > > It is very dangerous and inelegant to keep duplicate configuration even
> > in
> > > different storage media.
> > >
> > > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 下午12:30写道：
> > >
> > > > On Thu, Aug 20, 2020 at 11:42 AM vincixu <vi...@apache.org> wrote:
> > > >
> > > > > > 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.
> > > > >
> > > >
> > > > > because users will not have too many configurations
> > > >
> > > > Apache APISIX can support a large number of routes, which is an
> > important
> > > > feature for our users.
> > > >
> > > > Another case:
> > > >
> > > > the `service` or `upstream` object can be bound in `route`, when we
> > need
> > > to
> > > > delete the `service`
> > > > or `upstream` object, we need to confirm there is no route using it.
> if
> > > we
> > > > are using RDS, its easy for
> > > > this case.
> > > >
> > > > If we only use etcd, it is hard to support this case too.
> > > >
> > > >
> > > > >
> > > > > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
> > > > >
> > > > > > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org>
> 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 <ju...@classsoftware.com> 于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
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > *MembPhis*
> > > > My GitHub: https://github.com/membphis
> > > > Apache APISIX: https://github.com/apache/incubator-apisix
> > > >
> > >
> >
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by vincixu <vi...@apache.org>.
Relational database is not the only way.k8s implement all features(RBAC,
ABAC, cascade) we need but no relational databases.
Keep configuration in two places, it will bring a hard problem: how to
keep consistency.A problem that engineers have struggled for many years but
there has been no easy solution until now,I think it’s not worth
introducing such a problem to implement the mentioned features.
( I also have never seen a project using etcd and relational storage at the
same time to store the same data, )
wei jin <kv...@apache.org> 于2020年8月20日周四 下午4:04写道：
> We need a relational database to do some function extensions to meet some
> practical needs, such as authority management. But we also hope to keep
> apisix sufficiently convergent and focus on a high-performance gateway.
> APISIX should not be affected by external function extensions.
>
> vincixu <vi...@apache.org> 于2020年8月20日周四 下午3:53写道：
>
> > I don't think a lot of routes is a good practice.
> > But we can discuss how many routes APISIX plans to support. There is no
> > pressure on the front-end sorting of records less than 50,000 records(Our
> > team way).
> > If we plan to support large rotes query, paging and so on, we can load
> the
> > data into memory, and then simulate query and paging in the backend
> instead
> > of depend on another storage (the k8s apiserver way),
> > if we really need a storage that is easy to query, why not directly use
> it
> > as the configuration library of APISIX? Just like tyk did( using mongo as
> > configuration storage).
> > It is very dangerous and inelegant to keep duplicate configuration even
> in
> > different storage media.
> >
> > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 下午12:30写道：
> >
> > > On Thu, Aug 20, 2020 at 11:42 AM vincixu <vi...@apache.org> wrote:
> > >
> > > > > 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.
> > > >
> > >
> > > > because users will not have too many configurations
> > >
> > > Apache APISIX can support a large number of routes, which is an
> important
> > > feature for our users.
> > >
> > > Another case:
> > >
> > > the `service` or `upstream` object can be bound in `route`, when we
> need
> > to
> > > delete the `service`
> > > or `upstream` object, we need to confirm there is no route using it. if
> > we
> > > are using RDS, its easy for
> > > this case.
> > >
> > > If we only use etcd, it is hard to support this case too.
> > >
> > >
> > > >
> > > > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
> > > >
> > > > > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > *MembPhis*
> > > My GitHub: https://github.com/membphis
> > > Apache APISIX: https://github.com/apache/incubator-apisix
> > >
> >
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by wei jin <kv...@apache.org>.
We need a relational database to do some function extensions to meet some
practical needs, such as authority management. But we also hope to keep
apisix sufficiently convergent and focus on a high-performance gateway.
APISIX should not be affected by external function extensions.
vincixu <vi...@apache.org> 于2020年8月20日周四 下午3:53写道：
> I don't think a lot of routes is a good practice.
> But we can discuss how many routes APISIX plans to support. There is no
> pressure on the front-end sorting of records less than 50,000 records(Our
> team way).
> If we plan to support large rotes query, paging and so on, we can load the
> data into memory, and then simulate query and paging in the backend instead
> of depend on another storage (the k8s apiserver way),
> if we really need a storage that is easy to query, why not directly use it
> as the configuration library of APISIX? Just like tyk did( using mongo as
> configuration storage).
> It is very dangerous and inelegant to keep duplicate configuration even in
> different storage media.
>
> YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 下午12:30写道：
>
> > On Thu, Aug 20, 2020 at 11:42 AM vincixu <vi...@apache.org> wrote:
> >
> > > > 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.
> > >
> >
> > > because users will not have too many configurations
> >
> > Apache APISIX can support a large number of routes, which is an important
> > feature for our users.
> >
> > Another case:
> >
> > the `service` or `upstream` object can be bound in `route`, when we need
> to
> > delete the `service`
> > or `upstream` object, we need to confirm there is no route using it. if
> we
> > are using RDS, its easy for
> > this case.
> >
> > If we only use etcd, it is hard to support this case too.
> >
> >
> > >
> > > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
> > >
> > > > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
> > > >
> > >
> >
> >
> > --
> >
> > *MembPhis*
> > My GitHub: https://github.com/membphis
> > Apache APISIX: https://github.com/apache/incubator-apisix
> >
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by vincixu <vi...@apache.org>.
I don't think a lot of routes is a good practice.
But we can discuss how many routes APISIX plans to support. There is no
pressure on the front-end sorting of records less than 50,000 records(Our
team way).
If we plan to support large rotes query, paging and so on, we can load the
data into memory, and then simulate query and paging in the backend instead
of depend on another storage (the k8s apiserver way),
if we really need a storage that is easy to query, why not directly use it
as the configuration library of APISIX? Just like tyk did( using mongo as
configuration storage).
It is very dangerous and inelegant to keep duplicate configuration even in
different storage media.
YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 下午12:30写道：
> On Thu, Aug 20, 2020 at 11:42 AM vincixu <vi...@apache.org> wrote:
>
> > > 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.
> >
>
> > because users will not have too many configurations
>
> Apache APISIX can support a large number of routes, which is an important
> feature for our users.
>
> Another case:
>
> the `service` or `upstream` object can be bound in `route`, when we need to
> delete the `service`
> or `upstream` object, we need to confirm there is no route using it. if we
> are using RDS, its easy for
> this case.
>
> If we only use etcd, it is hard to support this case too.
>
>
> >
> > YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
> >
> > > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
> > >
> >
>
>
> --
>
> *MembPhis*
> My GitHub: https://github.com/membphis
> Apache APISIX: https://github.com/apache/incubator-apisix
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by YuanSheng Wang <me...@apache.org>.
On Thu, Aug 20, 2020 at 11:42 AM vincixu <vi...@apache.org> wrote:
> > 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.
>
> because users will not have too many configurations
Apache APISIX can support a large number of routes, which is an important
feature for our users.
Another case:
the `service` or `upstream` object can be bound in `route`, when we need to
delete the `service`
or `upstream` object, we need to confirm there is no route using it. if we
are using RDS, its easy for
this case.
If we only use etcd, it is hard to support this case too.
>
> YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
>
> > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
> >
>
--
*MembPhis*
My GitHub: https://github.com/membphis
Apache APISIX: https://github.com/apache/incubator-apisix
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by Ming Wen <we...@apache.org>.
etcd is used for the configuration of Apache APISIX.
If the management data (such as search, tag, status, etc.) is mixed, it
will affect the stability of the gateway.
Thanks,
Ming Wen, Apache APISIX & Apache SkyWalking
Twitter: _WenMing
vincixu <vi...@apache.org> 于2020年8月20日周四 上午11:42写道：
> > 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 <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
>
> > On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
> >
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by vincixu <vi...@apache.org>.
> 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 <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
> On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by Sheng Wu <wu...@gmail.com>.
You can't depend on MySQL, because of the license.
MySQL could be optional storage only.
Sheng Wu 吴晟
Twitter, wusheng1108
YuanSheng Wang <me...@apache.org> 于2020年8月20日周四 上午11:29写道：
> On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
>
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by YuanSheng Wang <me...@apache.org>.
On Thu, Aug 20, 2020 at 10:57 AM vincixu <vi...@apache.org> 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 <ju...@classsoftware.com> 于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
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by vincixu <vi...@apache.org>.
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.
This is really not a good idea. Dashboard should be kept simple and easy to
deploy, not another huge application.
Justin Mclean <ju...@classsoftware.com> 于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
Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite
Posted by Justin Mclean <ju...@classsoftware.com>.
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