As @ptyin mentioned, Golang offers better native support for Kubernetes.
The consideration for using Java is due to a lack of developer community,
but I believe that if the community remains insular, it will only be
limited to the Java ecosystem. The community should be open and welcome
more people to participate. In conclusion, I am inclined to use Golang to
write the Seata operator.


Warm regards,

Ji Min


Zhiyuan Lei <[email protected]> 于2023年12月10日周日 13:29写道:

> we use golang online,java sdk will meet some freaky problem,which is not
> necessary for us.
>
> I prefer golang
>
> yixia <[email protected]> 于 2023年12月10日周日 下午12:23写道:
>
> > golang would be more suitable because most of the projects and practices
> in
> > the cloud native field are based on golang. i vote for golang.
> >
> > 尹祥琨 <[email protected]> 于2023年12月9日周六 23:16写道:
> >
> > > Hi team,
> > >   The community is currently developing an Kubernetes operator to
> reduce
> > > the operation costs of Seata Server. We’d like to hear your opinions on
> > > implementing language. Some competitive candidates are listed below,
> > >
> > >   1. Go
> > >   Pros
> > >   Go is of vast majority when it comes to operator implementation.
> Since
> > > Kubernetes itself is written in Go, so this language interacts smoothly
> > > with Kubernetes API. Operator SDK provides a way to scaffold a Go-based
> > > operator and then implementing an operator means writing an imperative
> Go
> > > code.
> > >
> > >   2. Java
> > >   Pros
> > >   Most of developers in our community are familiar with Java.
> > >   Cons
> > >   Java Operator SDK are more experimental and less developed than
> > Operator
> > > SDK. Besides, Java Operator SDK uses third-party Kubernetes client
> (i.e.,
> > > Fabric8 Kubernetes Client) instead of official client, which is
> slightly
> > > worse than Go.
> > >
> > >   We need your experiences and insights. Please kindly discuss about
> your
> > > preference, and feel free to add comments or considerations influencing
> > > your choice.
> > > Best regards,
> > > Xiangkun Yin (尹祥琨)
> >
>

Reply via email to