For more cloud natively, gRPC and GraphQL are much better than either private tcp/socket or rest. Also, today, CLI is the real solution for communicating with platform like k8s.
Sheng Wu 吴晟 Twitter, wusheng1108 guo jiwei <[email protected]> 于2020年7月31日周五 下午12:30写道： > Hi, > I think we'd better support both of them. > Kernel-level API can trace or dump data to monitor ElasticJob and make > it more friendly to reliability and stability. > And high level can provide more base functional operations for users. > > Regards > Jiwei Guo (Tboy) > > > On Fri, Jul 31, 2020 at 12:02 PM [email protected] < > [email protected]> wrote: > > > Hi all, > > > > The current elasticjob's remote API used RESTful API for cloud and socket > > for lite, they are in-consist for now. > > > > I'd like to discuss how to deal with the remote APIs? > > > > Choose socket or RESTful only, or both? > > > > If both, we can design for the socket (used with nc or telnet) for > > kernel-level remote API, and add a additional module for RESTful API for > > high level usage. > > > > Any suggestions? > > > > ------------------ > > > > Sincerely, > > Liang Zhang (John) > > Apache ShardingSphere > > >
