[AndrewKemendo]

I really love this project and exactly what it’s trying to do.

There’s many things like this that I wish existed that make prototyping easier and faster and infrastructure a little bit nicer to use.

My concern is that because it’s a Nerfed version of the most basic/powerful/flexible implementation that is expected for a RESTful LAMP/SOAP application, it’s not gonna find its way into production applications, and as a result is going to be stuck as kind of prototyping tool.

My question to the author is have you figured out how to prevent that?

[marcua]

(author here)

Thank you for your kind words and the great question!

To your compliment: I agree ayb can help with easier prototyping today.

To your concern: I would not use ayb in a production setting today. To be explicit, while the roadmap [1] is long, I think that ayb will be useful in production once we've implemented a v1 of auth, permissions, persistence beyond the node, and isolation.

To "how to prevent that," here's a rough outline that I'm open to feedback on:

  - Implement the v1 features above

  - Host a public instance (and encourage others to, not trying to empire-build)

  - Build some fun applications on top of the public instance myself to stress test it

  - Encourage others to do the same and/or run some "learn SQL" classes to better understand where beginners get stuck and address those issues

Thank you again for your interest! Please share any feedback!

[1] https://github.com/marcua/ayb#roadmap

[AndrewKemendo]

I mean the fact that you have, what looks to my senior engineering manager eyes as, a coherent technical roadmap, puts you further along than almost every hobby level prototype tool.

Excited to see where it goes and if there’s an associated space here for integrating some form of environment management to wrap up all those other loose ends around dev.