<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 01/05/18 11:31, Flint WALRUS wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAG+53ua4c4YxsegV4GXM=HF7TGGamwOqvY4TT3QnVXLqNGM_uw@mail.gmail.com">Yes,
that’s was indeed the sens of my point.<br>
</blockquote>
<br>
I was just enforcing it, no worries! ;)<br>
<br>
<blockquote type="cite"
cite="mid:CAG+53ua4c4YxsegV4GXM=HF7TGGamwOqvY4TT3QnVXLqNGM_uw@mail.gmail.com"><br>
Openstack have to provide both endpoints type for a while for
backward compatibility in order to smooth the transition.<br>
<br>
For instance, that would be a good idea to contact postman devteam
once GraphQL will start to be integrated as it will allow a lot of
ops to keep their day to day tools by just having to convert their
existing collections of handful requests.<br>
</blockquote>
<br>
Shouldn't we have a common consensus before any project start
pushing its own GraphQL wheel?<br>
<br>
Also I wonder how GraphQL could open new architecture avenues for
OpenStack.<br>
For example, would that make sense to also have a GraphQL broker
linking OpenStack services?<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAG+53ua4c4YxsegV4GXM=HF7TGGamwOqvY4TT3QnVXLqNGM_uw@mail.gmail.com"><br>
Or alternatively to provide a tool with similar features at least.<br>
<div class="gmail_quote">
<div dir="ltr">Le mar. 1 mai 2018 à 03:18, Gilles Dubreuil <<a
href="mailto:gdubreui@redhat.com" moz-do-not-send="true">gdubreui@redhat.com</a>>
a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="m_-9120158338529253301moz-cite-prefix">On
30/04/18 20:16, Flint WALRUS wrote:<br>
</div>
<blockquote type="cite">I would very much second that
question! Indeed it have been one of my own wondering
since many times.<br>
<br>
Of course GraphQL is not intended to replace REST as is
and have to live in parallel </blockquote>
<br>
</div>
<div text="#000000" bgcolor="#FFFFFF"> Effectively a standard
initial architecture is to have GraphQL sitting aside (in
parallel) and wrapping REST and along the way develop
GrapgQL Schema.<br>
<br>
It's seems too early to tell but GraphQL being the next step
in API evolution it might ultimately replace REST.</div>
<div text="#000000" bgcolor="#FFFFFF"><br>
<br>
<blockquote type="cite">but it would likely and highly
accelerate all requests within heavily loaded environments</blockquote>
<br>
</div>
<div text="#000000" bgcolor="#FFFFFF"> +1</div>
<div text="#000000" bgcolor="#FFFFFF"><br>
<br>
<blockquote type="cite">.<br>
<br>
So +1 for this question.<br>
<div class="gmail_quote">
<div dir="ltr">Le lun. 30 avr. 2018 à 05:53, Gilles
Dubreuil <<a href="mailto:gdubreui@redhat.com"
target="_blank" moz-do-not-send="true">gdubreui@redhat.com</a>>
a écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Remember Boston's Summit presentation [1] about
GraphQL [2] and how it <br>
addresses REST limitations.<br>
I wonder if any project has been thinking about using
GraphQL. I haven't <br>
find any mention or pointers about it.<br>
<br>
GraphQL takes a complete different approach compared
to REST. So we can <br>
finally forget about REST API Description languages <br>
(OpenAPI/Swagger/WSDL/WADL/JSON-API/ETC) and HATEOS
(the hypermedia <br>
approach which doesn't describe how to use it).<br>
<br>
So, once passed the point where 'REST vs GraphQL' is
like comparing SQL <br>
and no-SQL DBMS and therefore have different
applications, there are no <br>
doubt the complexity of most OpenStack projects are
good candidates for <br>
GraphQL.<br>
<br>
Besides topics such as efficiency, decoupling, no
version management <br>
need there many other powerful features such as API
Schema out of the <br>
box and better automation down that track.<br>
<br>
It looks like the dream of a conduit between API
services and consumers <br>
might have finally come true so we could move-on an
worry about other <br>
things.<br>
<br>
So has anyone already starting looking into it?<br>
<br>
[1] <br>
<a
href="https://www.openstack.org/videos/boston-2017/building-modern-apis-with-graphql"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://www.openstack.org/videos/boston-2017/building-modern-apis-with-graphql</a><br>
[2] <a href="http://graphql.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://graphql.org</a><br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank"
moz-do-not-send="true">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
</blockquote>
<br>
</div>
<div text="#000000" bgcolor="#FFFFFF">
<pre class="m_-9120158338529253301moz-signature" cols="72">--
Gilles Dubreuil
Senior Software Engineer - Red Hat - Openstack DFG Integration
Email: <a class="m_-9120158338529253301moz-txt-link-abbreviated" href="mailto:gilles@redhat.com" target="_blank" moz-do-not-send="true">gilles@redhat.com</a>
GitHub/IRC: gildub
Mobile: +61 400 894 219
</pre>
</div>
</blockquote>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Gilles Dubreuil
Senior Software Engineer - Red Hat - Openstack DFG Integration
Email: <a class="moz-txt-link-abbreviated" href="mailto:gilles@redhat.com">gilles@redhat.com</a>
GitHub/IRC: gildub
Mobile: +61 400 894 219
</pre>
</body>
</html>