Discussion of Sanity's tech stack and query engine, with links to related resources.

I wonder if any Sanity insiders would share some description of their internal tech stack. What language is the GROQ DSL written in, and what were the influences / design decisions in developing it? Are the datastores document db's, or using JSON fields in PostgreSQL? Is the infrastructure on a cloud provider? And anything been written comparing Sanity to Prisma Server and Hasura?

There might be an opportunity coming up soon where you get some answers. Stay tuned 🙂
Meanwhile, there are some details to be had here:
https://gcppodcast.com/post/episode-232-sanity.io-with-simen-svale-skogsrud-and-knut-melvaer/

Thanks Knut!

But shortly: Query engine is written in mostly Go, a lot of the services in JS/TS, we use Postgres/Elastic, it runs on… google cloud using K8Ss and their CDN.

That makes a lot of sense, especially Elastic 😀 I was guessing the query engine might be in Ruby :ruby:

The Sanity precursor was: https://bengler.no/pebbles 🙂
And you could, at least theoretically, make a parser in Ruby as well:
https://www.sanity.io/blog/why-we-wrote-yet-another-parser-compiler#glush-the-project-6541c09fa22b

That's a great link, thanks. That's a really awesome library - didn't have any idea about it. Hope it stays maintained - I see last code commit on Glush is over a year ago. I've never used a scannerless parser generator before - but Glush creates Javascript parsers, which is incredibly useful!

Yeah – we have been busy on other things (including scaling the backend), but I think there will be more happening

Thanks again for the info. I'm reading through the sanity docs in detail and planning a test project. I've had studio and a gatsby front-end set up for a bit and an account, now to dig through and figure it out.