3 ms·
Just different risks. Adopting GraphQL without also adopting Facebook's exotic graph datastore is the unknown-unknown sort of risk that eventually leads to intr
by dustingetz 8y ago
Just different risks. Adopting GraphQL without also adopting Facebook's exotic graph datastore is the unknown-unknown sort of risk that eventually leads to intractable problems as demonstrated by Hibernate and a long history of ORM related failures, and it isn't even on the radar of 90% of GraphQL adopters, if HN comment activity is any indicator.
- headcanon 8y agocould you elaborate on that? we aren't using an ORM and are able to successfully batch queries to improve performance. Couple that with an understanding that the developer should not use overly-nested queries and its been working out fairly well so far, although we're not dealing with a massive user load yet.