I don't think "convenient" is an advantage. If APISIX can't outperform PostgREST or other similar projects, people still need to use them, instead of the "convenient" but "useless" solution.
Zexuan Luo <[email protected]> 于2021年3月25日周四 上午9:15写道： > > It is interesting. But there are many products in the market that > provide the REST wrapper. > > Why not use the wrapper directly as the upstream of APISIX? > > What are the advantages? > And what are the disadvantages? > > Joey Ma <[email protected]> 于2021年3月24日周三 下午6:40写道： > > > > On Wed, Mar 24, 2021 at 5:50 PM Ming Wen <[email protected]> wrote: > > > > > I also think it very interesting. > > > Is it more appropriate to implement this feature on the dashboard? > > > > > > > Hi, > > > > Thanks for the reply. > > > > May I ask that you mean we can implement this only on dashboard, without > > hacking APISIX? Sorry for not knowing how to achieve that. :-) > > > > Previously, I thought we needed to develop new plugins in APISIX and also > > provided related configurations in dashboard. For example, in dashboard we > > define a new route with the URI prefix of RESTful APIs, (e.g. > > `/api/users`). Then we enable the database plugin which has some config > > items like `endpoints`, `credentials` and `table name`. Once we finish the > > route creation, APISIX can automatically generates relevant routes `GET > > /api/users`, `GET api/users/$id`, `POST /api/users` and etc. Of course, we > > could also manually define the URIs of the routes via > > plugin configurations for fine-grained control. > > > > Looking forward to your insights. Thanks. > > > > > > > > > > Thanks, > > > Ming Wen, Apache APISIX PMC Chair > > > Twitter: _WenMing > > > > > > > > > Sheng Wu <[email protected]> 于2021年3月24日周三 下午5:17写道： > > > > > > > This seems very interesting. Are you planning to start from PostgreSQL > > > > as > > > > well? > > > > > > > > Sheng Wu 吴晟 > > > > Twitter, wusheng1108 > > > > > > > > > > > > Joey Ma <[email protected]> 于2021年3月24日周三 下午5:03写道： > > > > > > > > > Hi all, > > > > > > > > > > I'm writing here to hope to discuss with you guys about a new feature. > > > > It's > > > > > about to support exposing databases as web services. > > > > > > > > > > Please allow me to introduce my case. I'm now constructing a sort of > > > data > > > > > middle platform and use APISIX as the API gateway to handle the NS > > > > traffic. > > > > > One of the scenarios is to expose data stored in the database as web > > > > > services, mainly list/create/update/delete operations, for outer > > > clients. > > > > > As for now, we need to deploy an application for database access and > > > then > > > > > set it as the upstream of a route. For example, we use > > > > PostgREST/postgrest > > > > > [1] to serve RESTful APIs for Postgresql and make APSIX as the proxy. > > > > > > > > > > I believe that If APISIX can have this feature built-in, it will bring > > > > much > > > > > convenience, so I was wondering if APISIX is able to add support for > > > > > auto-exposing the database as uniform RESTful web services. If that, > > > the > > > > > only thing that users need to do is to fulfill the endpoint and > > > > > credentials of the database and then we are happy to see the routes > > > > > are > > > > > generated and ready for access. > > > > > > > > > > Looking forward to hearing from you. Much appreciated. > > > > > > > > > > > > > > > [1]: https://github.com/PostgREST/postgrest > > > > > > > > > > > > > > > Best regards, > > > > > Joey > > > > > > > > > > > >
