REST is not a perscription for how many joins you can do retrieving data. You don't need to force clients to compose http calls. You *can* write a query for `GET /things` without an ORM, schema in SDL, resolver code and client wrappers. It's allowed!
-
Show this thread
-
And I guarantee writing one optimized query against your data store is way faster in both authortime and runtime. Also maintenance! Way less deps..
1 reply 0 retweets 4 likesShow this thread -
Mastery of durable persistence is kinda the final boss for frontend dev. It's still a mess. And eh GraphQL doesn't solve this. It papers over the easiest part (transport) leaving the hardest as an exercise for the backend (fast queries) with waaaay more boilerplate.
3 replies 0 retweets 13 likesShow this thread -
Replying to @brianleroux
More boiler on the frontend, but the backend can basically be generated from database schema.
1 reply 0 retweets 0 likes -
Replying to @mikeal
Not that I've seen but ppl sure fo day that. Every one of these solutions dissolved into custom resolvers (custom queries!)
1 reply 0 retweets 0 likes -
Replying to @brianleroux @mikeal
Which is fine but also the point where you have to ask if this beautiful apparatus is actually doing anything..
1 reply 0 retweets 0 likes -
Replying to @brianleroux
my view has always been that we need to move past a model where databases take data "as is" and allow us to gain insights from it, rather than shaping data to meet the implementation of databases. as a result, i've always seen GraphQL as a stop-gap.
1 reply 0 retweets 0 likes -
Replying to @mikeal
Super agree. Thinking goin on w Cosmos is pretty awesome here tho I've yet to properly acquaint myself.
2 replies 0 retweets 1 like
Next time we meet. let's all get to know each other
-
-
Replying to @southpolesteve @brianleroux
definitely :) brian sort of live in San Francisco and I *actually* live here :)
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.