Tweetovi

Blokirali ste korisnika/cu @__xuorig__

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @__xuorig__

  1. Prikvačeni tweet
    24. lis 2019.

    New article, and new project 🚀 Just launched , where you'll be able to find all my new posts on 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: <=

    Prikaži ovu nit
    Poništi
  2. prije 3 sata

    Maybe an odd parallel, but personally this makes me think, just like in , 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 nit
    Poništi
  3. prije 3 sata

    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.

    Prikaži ovu nit
    Poništi
  4. prije 3 sata

    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:

    Prikaži ovu nit
    Poništi
  5. prije 3 sata

    Google used to offer a way to batch up many HTTP requests within one request using `multipart/mixed`, similar to OData's batch processing:

    Prikaži ovu nit
    Poništi
  6. prije 3 sata

    I stumbled upon this yesterday, and somehow it's super relevant to recent discussions (The "One Graph" to rule them all approach.)

    Prikaži ovu nit
    Poništi
  7. 2. velj

    It's almost your typical HTTP "request batching" in some ways 🤔

    Prikaži ovu nit
    Poništi
  8. 2. velj

    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 nit
    Poništi
  9. 2. velj

    I like Airbnb's original approach (Not sure if it has changed since, cc ) 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"

    Prikaži ovu nit
    Poništi
  10. 1. velj

    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 nit
    Poništi
  11. 1. velj

    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 nit
    Poništi
  12. 1. velj

    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 nit
    Poništi
  13. 1. velj

    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 nit
    Poništi
  14. 1. velj

    1/ I keep coming back to 's post on GraphQL & BFFs: There are so many great points in there. While it's true allows multiple client experiences to co-exist within a same API, that's only one part of the BFF pattern..

    Prikaži ovu nit
    Poništi
  15. proslijedio/la je Tweet
    1. velj

    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 nit
    Poništi
  16. 31. sij

    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: Anybody doing similar things? Considering trying to standardize it 🤔

    Poništi
  17. 31. sij
    Poništi
  18. 31. sij
    Poništi
  19. proslijedio/la je Tweet
    30. sij
    Poništi
  20. proslijedio/la je Tweet
    30. sij

    Missed this when it was first published, but happy to see my home and native land publishing guidelines! 🇨🇦😀

    Poništi
  21. 30. sij
    Prikaži ovu nit
    Poniš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.

    Možda bi vam se svidjelo i ovo:

    ·