You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shardingsphere.apache.org by "zhangliang@apache.org" <zh...@apache.org> on 2020/07/31 04:01:31 UTC
[ElasticJob] Discuss about use RESTful API or socket for elasticjob's
remote API
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
Re: [ElasticJob] Discuss about use RESTful API or socket for
elasticjob's remote API
Posted by "zhangliang@apache.org" <zh...@apache.org>.
How about using gRPC for remote API only?
------------------
Sincerely,
Liang Zhang (John)
Apache ShardingSphere
Sheng Wu <wu...@gmail.com> 于2020年7月31日周五 下午1:09写道：
> 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 <te...@apache.org> 于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 zhangliang@apache.org <
> > zhangliang@apache.org> 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
> > >
> >
>
Re: [ElasticJob] Discuss about use RESTful API or socket for
elasticjob's remote API
Posted by Sheng Wu <wu...@gmail.com>.
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 <te...@apache.org> 于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 zhangliang@apache.org <
> zhangliang@apache.org> 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
> >
>
Re: [ElasticJob] Discuss about use RESTful API or socket for
elasticjob's remote API
Posted by guo jiwei <te...@apache.org>.
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 zhangliang@apache.org <
zhangliang@apache.org> 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
>