I agree with Willem. After looking at what GraphQL is doing, I can't figure out how java-chassis will benefit from this component. May be you can write a small demonstration using java-chassis and we can go on for further discussion.
------------------ ???????? ------------------ ??????: "willem.jiang"<willem.ji...@gmail.com>; ????????: 2019??3??30??(??????) ????5:24 ??????: "dev"<dev@servicecomb.apache.org>; ????: "Vinay Murudi"<vin...@huawei.com>; "krishna.m.kumar"<krishna.m.ku...@huawei.com>; "sanil.kumar"<sanil.ku...@huawei.com>; ????: Re: [PROPOSAL] [GSOC 2019] Adding the GraphQL support for RestServices in ServiceComb SDK. Hi Asif?? I just had a quick look for the website. It looks like the GraphQL could reduce the response message size by specifying the interested data in requery . As the service is consumed by JS front end, I'm not sure java-chassis's service consumer can leverage this feature. From the implementation side, as Java chassis is based on the Open API module to provide the service governance support, it could be a challenge for us to bridge the GraphQL with Java-chassis. Do you have any idea about that? Willem Jiang Twitter: willemjiang Weibo: ????willem On Fri, Mar 29, 2019 at 9:56 PM Mohammad Asif Siddiqui <asifdxtr...@apache.org> wrote: > > Hello All, > > GraphQL[1] is a query language for APIs and a runtime for fulfilling those > queries with your existing data. GraphQL provides a complete and > understandable description of the data in your API, gives clients the power > to ask for exactly what they need and nothing more, makes it easier to > evolve APIs over time, and enables powerful developer tools. > > > Already lot of big players use GraphQL in their production and it will be > really a great idea to add the support of GraphQL in our existing REST > services so that the microservices using our sdk gets privilege to get only > those data from the API which they require. > > > > Some of the benefits for the adding GraphQL support will be : > > - Lot of microservices are common services which are used by many other > consumers so the consumers can filter out the data which they require. > - Reduce the traffic load between the inter micro-service communication. > - Get relevant data in a minimal API calls. > > > So IMO we can wrap the GraphQL with our existing API services so that the > providers/consumers can use it and also the inter-communication between > sdk??s and service-center can leverage this. > > > So I would like to propose this idea in GSOC 2019[2] so that university > students can pick it up and implement it. > > > Please let me know your opinion on this. > > > [1] https://graphql.org/ > > [2] https://summerofcode.withgoogle.com/ > > > > Regards > > Mohammad Asif Siddiqui > > Senior Technical Leader | Apache IPMC | ServiceComb PMC > > Bengaluru-560066, Karnataka > > Tel: +91-80-49160700 Ext 72234 II Mob: 9972855443 Email: asifdi...@gmail.com > <mailto:asifdi...@gmail.com>
