Re:Backend-as-a-service for web apps?
by davewasmer on Wednesday December 28, 2011 @11:28PM
(#3402518)
True, but don't those services require schema definitions and similar setup? It seems like a lot of prototyping could be sped up by simply inferring relationships based on RESTful URLs and relying on schema-less storage.
[ Parent
| on HN ]
Seems like that would only work in the simplest of cases. And then why would I pay someone for the backend of a trivial app?
Re:Backend-as-a-service for web apps?
by davewasmer on Thursday December 29, 2011 @12:07AM
(#3402592)
I'm not sure. It certainly couldn't handle every use case, but maybe with some convention-style configurations (e.g. a record created via a POST to /users would hash any "password" field) you could handle a bunch of typical web app scenarios.
And if that doesn't work, perhaps the schema-less prototyping is a free tier with a more robust backend service offering for the paid tier?
"The password field is handled differently than the others; it is encrypted on the server and never returned to any client request."