APIs & Distributed Systems @Netflix

Montreal, Canada
Marc-André Giroux retweeted
i don’t know how else to describe it, but there’s a kind of person who sincerely believes they contribute value by relaying your ask to chatgpt and then relaying the output right back to you i’ve interviewed candidates who acted like showing how they think (coming up with a plan, explaining decisions) is an archaic demand, that “that just isn’t what work is anymore” but then what is it? you’re interviewing for a job that’s 100x the cost of a year of chatgpt pro—if all you are is a slower way to prompt an agent, why hire you? there’s still so much value people can contribute! but, as always, they require thought and effort
There's no point at which turning your brain off will work: danluu.com/brain-off/
33
51
1,409
155,636
What an amazing coincidence that GraphQL was also the perfect API for LLMs. Very natural pivot for GraphQL Federation companies

ALT Straight Face Trying Not To Laugh GIF

2
4
593
Marc-André Giroux retweeted
Our next GraphQL star is @__xuorig__ who literally wrote the book on "Production Ready GraphQL"! Marc-Andre's voice in our ecosystem as an emeritus TSC member & author of several high-quality blog posts is super valuable - thank you Marc-Andre!
1
6
2,024
😍 You know it's going to be a good post when it's by @vmg
"the semantic analysis we perform in Vitess is advanced enough that, through careful integration with the upstream MySQL server and its information schema, it can be used to statically type the AST of the SQL expressions we were executing." planetscale.com/blog/faster-…
1
9
1,429
Bored of Rust vs X posts that compare a lang a team has been working with for years vs what can be explained by unfamiliarity with Rust. Oh no we unwrap() on a map get and it panics! Control for familiarity with the language, and I feel like a lot of stuff starts looking similar.
494
show the baseline numbers
Replying to @graphqlweekly
Apollo is introducing a new native query planner that's specifically designed for Federation 2.0. The update brings impressive improvements: - 10x faster query planning - 2.9x lower CPU usage - 2.2x reduced memory consumption
9
1,322
Marc-André Giroux retweeted
Practical advice on the share vs. duplicate types debate
New post 🌶️ The MOIST Principle for GraphQL Schema Design buff.ly/428f5pO
1
7
966
Marc-André Giroux retweeted
🔥🔥Latest @graphqlweekly is 🔥🔥 @__xuorig__ with principles of schema design @ThreeBrewMates with a demo of @apollographql Connectors and oData @HasuraHQ Introducing GraphQL Subscriptions to Hasura DDN @losoviz showing ChatGPT with GatoGraphQL Things are happening!
1
4
9
960
Marc-André Giroux retweeted
New post 🌶️ The MOIST Principle for GraphQL Schema Design buff.ly/428f5pO
2
10
30
3,514
lol nothing to do federation, and pulling 99% out of thin air. A LOT of GraphQL APIs out there actually use `/graphql` (Facebook, Shopify, GitHub, Walmart, Wayfair, first 5 that came to mind) on the same domain. You found an issue on gusto, that's OK, no need to generalize.
Replying to @nateberkopec
With GraphQL, people see it as a separate resource from the app, so they put it under a subdomain >99% of the time. Makes sense given how GQL is suppose to "federate". With REST APIs, we far more often just serve it straight from the same app/same subdomain. Common in Rails.
1
17
1,427
Deeply unserious critique. Not "fashionable" at all, and it's probably even more common to have`api.*.com` in "rest" APIs lol.
One subtle way GraphQL is slower than the REST equivalent: It's fashionable to put your GQL API on graphql.*.com. The browser url is usually *.com or app.*.com. Every request now gets CORS preflighted, adding 1 addt'l network round-trip to every request. 💀
2
1
26
2,160
Serious take about GraphQL performance since that is very often brought up these days: GraphQL's inherent overhead is mostly limited to its parsing/validation step and its execution engine logic. Eliminating or keeping that to a minimum is important and generally easy.
6
3
39
2,807
"resolvers" are almost always at the source of issues. Compared with endpoint-based APIs, in GraphQL, field resolution operates with very local information and has a smaller "horizon" for optimization.
1
6
537
Most commonly this leads to data-loading issues. Note that a sufficiently complex codebase will lead to very similar problems no matter the API style. GraphQL does put them in front of you sooner in the process.
1
9
509