Manish is the Chief decision maker at Dgraph. He got thrust into distributed systems right out of college, working on real time web indexing system at Google. He then lead various projects to consolidate and serve knowledge graph right behind web search. Implementing GTD and Zero Waste practices, Manish is into efficient and minimalist living. He loves cycling, swimming and ultra light travelling.
The ‘Load a sample app’ feature is great! Will there be the ability to edit the front-end code and see the changes as well? To go further, will there be an ability to host custom apps with custom domains?
I’m really happy about the native queries feature! Will be native Javascript queries in Slash GraphQL available also in the Dgraph directly? When we can expect that this feature will be available?
More of a discussion rather than question, but I’m curious how you and Dgraph team are gonna respond to GQL Standard (which is currently in proposal) since that one might have a chance to work differently compared to GraphQL. Will you strive to make both of them compatible to each other?
Can we deploy Slash to own cloud on OVH for instance and how will that be charged? We have apps with LOTS of data and it is too expensive to host in AWS or GCP.
Great Question! Most serverless frameworks just hide the number of servers you are running. They say give me a javascript function and we’ll run it for you. But you still have to write code, connect to a database, etc!!!
We are one step further - backendless. Just give us your schema and we’ll set up everything.
Do you have any recommendations on how to do development work using this? I know this is very open ended… but should we do dev in a Docker container, on our Mac, etc?
Yup, I think a lot of people will be using this pattern, slowly moving one service at a time over to Slash GraphQL. We are currently working with apollo federation.
Personally? I develop with Slash. The free tier and command line means you can just spin up backends on a whim. So spin up a backend in the morning, keep applying a schema, and shut down in the evening.
Slash GraphQL is powered by Dgraph, so you can run dgraph locally if you’d like to. We wanted to make sure that you avoid vendor lock in if you ever want to move away, so there is no extra features that slash adds over open source Dgraph GraphQL (other than whatever it takes to manage it in the cloud).
But that said, I love to just work with Slash. The CLI lets you spin up a backend, and just use it.
I have tried Hasura once. There I need a separate db endpoint to set up the backend. But As per I have understood, I don’t have to care about db in slash graphql. I just need a schema and my backed is up and running. Am I correct?
slash.dgraph.io
Will be native Javascript queries in Slash GraphQL available also in the Dgraph directly? When we can expect that this feature will be available? 
