If you don't want to incur a bunch of performance a, you know, crushing stuff, you can look at doing something like a serverless function. Nowadays, we're getting all sorts of cool new things in the client side via wazm and who knows what? It's true. And also, one neat thing about graph cs, you can do this thing called schema stitching. Which means tha, the actual work performed in the graph. Caapi could live in seven or eight different serves, right? Thete doesn't have to be on one single server, but it can be surface vo one api. Totally. Oh, we forgot the cashing layer. Wont talk

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode