Hacker News new | past | comments | ask | show | jobs | submit login

If such a project were based on top of an RDBMS, would you still expect a document/KV-oriented API, or one more SQL-ish?



Honestly I don't mind. A document API with a little manipulation on the front-end would be fine, as long as the back-end has some way of running through the relations.

A SQL-ish API might even be better, although I can see some pitfalls. Maybe base it on GraphQL as a compromise?

Either way, I'd love to have something like this.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: