It's possible to use the same design docs both for client- and serverside validation. They don't look pretty, but maintaining them in readable JS and deploying them via CI works fine.
Apart from Proxy Auth and JWT, just using basic Auth/session + a backend like Superlogin works for simple use cases.
But sure, you'll want to set up rate limits etc using something like HaProxy once you have actual customer data on a CouchDB instance.
Apart from Proxy Auth and JWT, just using basic Auth/session + a backend like Superlogin works for simple use cases.
But sure, you'll want to set up rate limits etc using something like HaProxy once you have actual customer data on a CouchDB instance.