Well, if we consider the restful module as a separate process, then we have to re-implement all the authorization module in the restful (client sends request -> restful server assign a token to the client, and cache the privileges of the client.)
Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang <[email protected]> 于2021年1月11日周一 上午12:32写道： > Hi Giorgio, > > Thanks, your explanation is detailed. > > Currently the restAPI (especially for Grafana query) is designed to > generate a queryPlan directly without a SQL parser. > > If we make the restful service independently, I need to redesign that API. > (It is ok for me, but just want to hear more voices). > > Best, > ----------------------------------- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Giorgio Zoppi <[email protected]> 于2021年1月10日周日 下午11:13写道： > >> Hello, >> I would apply the single responsibility thing here and create a >> microservice independent by the main process here. The only burden is to >> manage >> the deploy but with docker compose comes easy. The advantages are: >> - you can put redis in the middle if you want to cache results and lower >> the latency a lot. >> - you can benchmark it better. >> - you can scale the service and the iotdb independently. >> - one person can only care to update/compile/maintain just the service >> without thinking too much. >> - smaller, simple, minimal is good. >> >> The discussion is open. >> Best Regards, >> Giorgio >> >
