Tweetovi
- Tweetovi, trenutna stranica.
- Tweetovi i odgovori
- Medijski sadržaj
Blokirali ste korisnika/cu @__xuorig__
Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @__xuorig__
-
Prikvačeni tweet
New article, and new project
Just launched https://productionreadygraphql.com , where you'll be able to find all my new posts on #GraphQL from now on. I'll also be announcing more things around the concept soon
It's on Twitter! Give it a follow if you'd like:
@prodreadygql <=Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Maybe an odd parallel, but personally this makes me think, just like in https://twitter.com/__xuorig__/status/1223685722042966016 …, that the "One Graph" pattern should not be necessarily recommended as a hard rule in GraphQL, and be highly dependent on both the architectural and cultural context of an organization
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Note that they still will be supporting what they call "Homogenous" batch requests (requests that are all linked to one underlying API) but not batching across different APIs.pic.twitter.com/FIX4CdMR6U
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
As an organization's underlying architecture evolves, especially as it becomes more distributed, offering that one big shared proxy approach may become harder and harder, and here Google decided no longer to support it:pic.twitter.com/bztLR84JnF
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Google used to offer a way to batch up many HTTP requests within one request using `multipart/mixed`, similar to OData's batch processing: https://www.odata.org/documentation/odata-version-3-0/batch-processing/ …
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
I stumbled upon this yesterday, and somehow it's super relevant to recent
#GraphQL discussions (The "One Graph" to rule them all approach.)https://developers.googleblog.com/2018/03/discontinuing-support-for-json-rpc-and.html …Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
It's almost your typical HTTP "request batching" in some ways
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
I used to be skeptical due to the fact you don't get the benefits of "querying across relationships" that comes with GraphQL, but it's a tradeoff that makes a ton of sense in the right context since it removes most of the need for complex query plans / federation.
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
I like Airbnb's original approach (Not sure if it has changed since, cc
@skevy ) to "schema-stitching". It's pragmatical and avoids complexity that comes with stitching by well isolating use cases and not allowing "cross-service nested queries"https://medium.com/airbnb-engineering/reconciling-graphql-and-thrift-at-airbnb-a97e8d290712 …Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
5/ Not sure where I'm going to with this. But maybe that the "One Graph" utopia a lot of organization seem to be going for has limits, and that there is value in fully autonomous experience based APIs, even with GraphQL.
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
4/ It's easy to fall into the trap of an ultra generic one-size-fits-all GraphQL API, in which case we definitely don't have anything close to something the BFF pattern would provide us.
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
3/ A single GraphQL server is not inherently a valid comparison to BFF. I think it definitely can come close in terms of supporting multiple client experiences in terms of *representation*, but requires extra effort to allow for full autonomy.
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
2/ Main goal here is full autonomy of client experiences. Phil mentions things like a certain client experience choosing a completely different serialization format, or even a different caching strategy for example. Something that would definitely require multiple "GraphQL BFFs".
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
1/ I keep coming back to
@pcalcado's post on GraphQL & BFFs: https://philcalcado.com/2019/07/12/some_thoughts_graphql_bff.html … There are so many great points in there. While it's true#GraphQL allows multiple client experiences to co-exist within a same API, that's only one part of the BFF pattern..Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Marc-André Giroux proslijedio/la je Tweet
I was working on reviews this week and keep coming back to something: how important it is for docs teams to have dedicated engineering help. So here’s a story about the impact engineers have had on my team.
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
#GraphQL RFC Idea: *GraphQL-Path*. At GitHub we've unofficially been using a way for tools to point to a schema member. Even found its way into GraphQL-Ruby: https://github.com/rmosolgo/graphql-ruby/blob/master/lib/graphql/schema.rb#L433-L444 … Anybody doing similar things? Considering trying to standardize it
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Definitely tuning in today!


https://twitter.com/shrutikapoor08/status/1223047584689750016 …Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Marc-André Giroux proslijedio/la je TweetHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Marc-André Giroux proslijedio/la je Tweet
Missed this when it was first published, but happy to see my home and native land publishing
#API guidelines!#ehPIs
https://twitter.com/TDAndrea23/status/1143319335974375434 …Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
APIs
