Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Production PouchDB with AWS DB Service Backend #320

Open
Brainsway-Cloud opened this issue Apr 26, 2018 · 3 comments
Open

Production PouchDB with AWS DB Service Backend #320

Brainsway-Cloud opened this issue Apr 26, 2018 · 3 comments

Comments

@Brainsway-Cloud
Copy link

Brainsway-Cloud commented Apr 26, 2018

I've built a PouchDB/CouchDB offline-first solution using a CouchDB cluster on AWS.

Now my customer is suddenly excited about serverless and is requiring that I use one of the AWS databases-as-a-service so he won't need to administer a CouchDB cluster. Fair enough.

I started looking at using pouchDB LevelUp and https://github.com/davidguttman/dynamodown but before I continue:

  1. There are ominous warnings in the Pouch documentation about using a levelUP backend in production that hasn't been tested/approved and the dynamodown page admits it doesn't pass all tests for unknown reasons.

  2. It is not clear to me what kind of performance or feature limitations are incurred by using LevelUP backends. Are people using any of these in production? Am I going "where no man has gone before" and will I regret it?

  3. Could I just do pouchdb over leveldb and no servers running at all? What would I be missing? Just clustering?

The main question: Is there a tested robust performant full-featured PouchDB for the server side that can use an AWS DB as a backend?

@garrensmith
Copy link
Member

Hi @Brainsway-Cloud, I think you definitely going where no one has been before. I'm not aware of a dynamodb supported backend. The only adapters that are tested with pouchdb are all the browser ones and leveldb. Using anything outside of that for production is pretty risky unless you happy doing a fair amount of testing, debugging and fixing.

@Brainsway-Cloud
Copy link
Author

Brainsway-Cloud commented Apr 26, 2018

Pouch has lots of options client-side but for a production quality server-side, sounds like the only safe way I could avoid administering my own database servers would be to use Cloudant?

@acristu
Copy link

acristu commented Aug 29, 2018

Hi, if someone were to attempt to go "where no one has been before" could you perhaps make a list of things we should focus on with priority in order to increase the stability and performance of pouchdb on nodejs.
My question is also related related to #136 but for this specific use case of supporting a backend that is not tested by the core pouchdb team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants