@IvanChepurnyi@brentwpeterson Where as an IOT device sending sensor data REST could be faster. Then again something on top of UDP would be “faster” in this hypothetical example…
@IvanChepurnyi@brentwpeterson In the context of a mobile application, one request to retrieve just the data (e.g user, friends, posts, ads) needed to render the UI can be more performant than managing multiple network requests.
@IvanChepurnyi@brentwpeterson GraphQL isn’t prescriptive on backend implementation. Similar to how a REST-like endpoint for an e-commerce cart model doesn’t automatically avoid an n+1 problem by loading product details of a CartItem. One GraphQL query may translate to *many* REST calls and avoids overfetching
@IvanChepurnyi@brentwpeterson Single query performance isn’t a good metric to consider since it’s not where GraphQL fits in. Schema aside, the tooling and developer experience with GraphQL is much better than REST-like services IMO. OpenAPI is ok but still not as nice/flexible as GraphQL.
@jillrep it was wild when we got there shortly after 5, went to have dinner and it wasn’t any better so we bailed. Heard it was still about 3 hours at 11pm
@inminivanhell@City_of_Irvine@LAGalaxy@orangecountysc Maybe they can reuse Todd Spitzer’s “No LA in OC” campaign signs/slogan. Can we count on Tammy Kim to fear monger and warn Irvine residents about “sketchy” LA fútbol fans coming to their pristine suburb?