Alternatives to Pouchdb logo

Alternatives to Pouchdb

MongoDB, SQLite, CouchDB, Firebase, and Hoodie are the most popular alternatives and competitors to Pouchdb.
110
201
+ 1
5

What is Pouchdb and what are its top alternatives?

PouchDB enables applications to store data locally while offline, then synchronize it with CouchDB and compatible servers when the application is back online, keeping the user's data in sync no matter where they next login.
Pouchdb is a tool in the Databases category of a tech stack.
Pouchdb is an open source tool with 14.6K GitHub stars and 1.4K GitHub forks. Here’s a link to Pouchdb's open source repository on GitHub

Top Alternatives to Pouchdb

  • MongoDB

    MongoDB

    MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding. ...

  • SQLite

    SQLite

    SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file. ...

  • CouchDB

    CouchDB

    Apache CouchDB is a database that uses JSON for documents, JavaScript for MapReduce indexes, and regular HTTP for its API. CouchDB is a database that completely embraces the web. Store your data with JSON documents. Access your documents and query your indexes with your web browser, via HTTP. Index, combine, and transform your documents with JavaScript. ...

  • Firebase

    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Hoodie

    Hoodie

    We want to enable you to build complete web apps in days, without having to worry about backends, databases or servers, all with an open source library that's as simple to use as jQuery. ...

  • LokiJS

    LokiJS

    LokiJS is a document oriented database written in javascript, published under MIT License. Its purpose is to store javascript objects as documents in a nosql fashion and retrieve them with a similar mechanism. Runs in node (including cordova/phonegap and node-webkit), nativescript and the browser. ...

  • Couchbase

    Couchbase

    Developed as an alternative to traditionally inflexible SQL databases, the Couchbase NoSQL database is built on an open source foundation and architected to help developers solve real-world problems and meet high scalability demands. ...

  • IndexedDB

    IndexedDB

    This API uses indexes to enable high-performance searches of this data. While Web Storage is useful for storing smaller amounts of data, it is less useful for storing larger amounts of structured data. ...

Pouchdb alternatives & related posts

MongoDB logo

MongoDB

64.6K
53.8K
4.1K
The database for giant ideas
64.6K
53.8K
+ 1
4.1K
PROS OF MONGODB
  • 824
    Document-oriented storage
  • 591
    No sql
  • 546
    Ease of use
  • 465
    Fast
  • 406
    High performance
  • 256
    Free
  • 215
    Open source
  • 179
    Flexible
  • 142
    Replication & high availability
  • 109
    Easy to maintain
  • 41
    Querying
  • 37
    Easy scalability
  • 36
    Auto-sharding
  • 35
    High availability
  • 31
    Map/reduce
  • 26
    Document database
  • 24
    Easy setup
  • 24
    Full index support
  • 15
    Reliable
  • 14
    Fast in-place updates
  • 13
    Agile programming, flexible, fast
  • 11
    No database migrations
  • 7
    Easy integration with Node.Js
  • 7
    Enterprise
  • 5
    Enterprise Support
  • 4
    Great NoSQL DB
  • 3
    Aggregation Framework
  • 3
    Support for many languages through different drivers
  • 3
    Drivers support is good
  • 2
    Schemaless
  • 2
    Easy to Scale
  • 2
    Fast
  • 2
    Awesome
  • 2
    Managed service
  • 1
    Consistent
CONS OF MONGODB
  • 5
    Very slowly for connected models that require joins
  • 3
    Not acid compliant
  • 1
    Proprietary query language

related MongoDB posts

Jeyabalaji Subramanian

Recently we were looking at a few robust and cost-effective ways of replicating the data that resides in our production MongoDB to a PostgreSQL database for data warehousing and business intelligence.

We set ourselves the following criteria for the optimal tool that would do this job: - The data replication must be near real-time, yet it should NOT impact the production database - The data replication must be horizontally scalable (based on the load), asynchronous & crash-resilient

Based on the above criteria, we selected the following tools to perform the end to end data replication:

We chose MongoDB Stitch for picking up the changes in the source database. It is the serverless platform from MongoDB. One of the services offered by MongoDB Stitch is Stitch Triggers. Using stitch triggers, you can execute a serverless function (in Node.js) in real time in response to changes in the database. When there are a lot of database changes, Stitch automatically "feeds forward" these changes through an asynchronous queue.

We chose Amazon SQS as the pipe / message backbone for communicating the changes from MongoDB to our own replication service. Interestingly enough, MongoDB stitch offers integration with AWS services.

In the Node.js function, we wrote minimal functionality to communicate the database changes (insert / update / delete / replace) to Amazon SQS.

Next we wrote a minimal micro-service in Python to listen to the message events on SQS, pickup the data payload & mirror the DB changes on to the target Data warehouse. We implemented source data to target data translation by modelling target table structures through SQLAlchemy . We deployed this micro-service as AWS Lambda with Zappa. With Zappa, deploying your services as event-driven & horizontally scalable Lambda service is dumb-easy.

In the end, we got to implement a highly scalable near realtime Change Data Replication service that "works" and deployed to production in a matter of few days!

See more
Robert Zuber

We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

See more
SQLite logo

SQLite

12.3K
9.6K
528
A software library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine
12.3K
9.6K
+ 1
528
PROS OF SQLITE
  • 160
    Lightweight
  • 134
    Portable
  • 121
    Simple
  • 80
    Sql
  • 28
    Preinstalled on iOS and Android
  • 2
    Tcl integration
  • 1
    Free
  • 1
    Telefon
  • 1
    Portable A database on my USB 'love it'
CONS OF SQLITE
  • 2
    Not for multi-process of multithreaded apps
  • 1
    Needs different binaries for each platform

related SQLite posts

Dimelo Waterson
Shared insights
on
PostgreSQLPostgreSQLMySQLMySQLSQLiteSQLite

I need to add a DBMS to my stack, but I don't know which. I'm tempted to learn SQLite since it would be useful to me with its focus on local access without concurrency. However, doing so feels like I would be defeating the purpose of trying to expand my skill set since it seems like most enterprise applications have the opposite requirements.

To be able to apply what I learn to more projects, what should I try to learn? MySQL? PostgreSQL? Something else? Is there a comfortable middle ground between high applicability and ease of use?

See more
Christian Stefanescu
Head of IT at lawpilots · | 3 upvotes · 10.4K views
Shared insights
on
DjangoDjangoSQLiteSQLitePostgreSQLPostgreSQL

While I love and use PostgreSQL , I would definitely recommend having a look at SQLite as well. It can be a solid database for lots of applications and it brings some advantages in terms of handling: you don't need a server running, which makes things like testing, deploying or backing up databases much easier. Through the ORM in Django you are one abstraction level away from your database anyway and switching later on is definitely an option, but I believe SQLite is very good for pretty much all the small applications you can think of.

See more
CouchDB logo

CouchDB

445
498
139
HTTP + JSON document database with Map Reduce views and peer-based replication
445
498
+ 1
139
PROS OF COUCHDB
  • 43
    JSON
  • 30
    Open source
  • 18
    Highly available
  • 12
    Partition tolerant
  • 11
    Eventual consistency
  • 7
    Sync
  • 5
    REST API
  • 4
    Attachments mechanism to docs
  • 4
    Multi master replication
  • 3
    Changes feed
  • 1
    REST interface
  • 1
    js- and erlang-views
CONS OF COUCHDB
    Be the first to leave a con

    related CouchDB posts

    Jonathan Pugh
    Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 1.6M views

    I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

    For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

    Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

    I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

    I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

    I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

    I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

    For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

    For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

    For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

    I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

    So that's my latest mobile stack. What tools do you use? Have you tried these ones?

    See more
    Gabriel Pa

    We implemented our first large scale EPR application from naologic.com using CouchDB .

    Very fast, replication works great, doesn't consume much RAM, queries are blazing fast but we found a problem: the queries were very hard to write, it took a long time to figure out the API, we had to go and write our own @nodejs library to make it work properly.

    It lost most of its support. Since then, we migrated to Couchbase and the learning curve was steep but all worth it. Memcached indexing out of the box, full text search works great.

    See more
    Firebase logo

    Firebase

    28.1K
    23.8K
    1.9K
    The Realtime App Platform
    28.1K
    23.8K
    + 1
    1.9K
    PROS OF FIREBASE
    • 361
      Realtime backend made easy
    • 264
      Fast and responsive
    • 234
      Easy setup
    • 207
      Real-time
    • 186
      JSON
    • 128
      Free
    • 121
      Backed by google
    • 81
      Angular adaptor
    • 63
      Reliable
    • 36
      Great customer support
    • 26
      Great documentation
    • 23
      Real-time synchronization
    • 20
      Mobile friendly
    • 17
      Rapid prototyping
    • 12
      Great security
    • 11
      Automatic scaling
    • 10
      Freakingly awesome
    • 8
      Chat
    • 8
      Angularfire is an amazing addition!
    • 8
      Super fast development
    • 6
      Awesome next-gen backend
    • 6
      Ios adaptor
    • 5
      Built in user auth/oauth
    • 5
      Firebase hosting
    • 4
      Speed of light
    • 4
      Very easy to use
    • 3
      It's made development super fast
    • 3
      Great
    • 3
      Brilliant for startups
    • 2
      Great all-round functionality
    • 2
      Low battery consumption
    • 2
      I can quickly create static web apps with no backend
    • 2
      The concurrent updates create a great experience
    • 2
      JS Offline and Sync suport
    • 1
      Faster workflow
    • 1
      Large
    • 1
      Serverless
    • 1
      .net
    • 1
      Free SSL
    • 1
      Good Free Limits
    • 1
      Push notification
    • 1
      Easy to use
    • 1
      Easy Reactjs integration
    CONS OF FIREBASE
    • 29
      Can become expensive
    • 15
      No open source, you depend on external company
    • 15
      Scalability is not infinite
    • 9
      Not Flexible Enough
    • 5
      Cant filter queries
    • 3
      Very unstable server
    • 2
      No Relational Data
    • 2
      Too many errors
    • 1
      No offline sync

    related Firebase posts

    Stephen Gheysens
    Senior Solutions Engineer at Twilio · | 14 upvotes · 358.3K views

    Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

    My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

    See more
    Tassanai Singprom

    This is my stack in Application & Data

    JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

    My Utilities Tools

    Google Analytics Postman Elasticsearch

    My Devops Tools

    Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

    My Business Tools

    Slack

    See more
    Hoodie logo

    Hoodie

    11
    23
    16
    A fast offline-first architecture for webapps. Super-simple user management & storage. Great for mobile.
    11
    23
    + 1
    16
    PROS OF HOODIE
    • 4
      Reduces boilerplate
    • 4
      JSON
    • 3
      Offline first
    • 2
      Open source
    • 2
      Mobile friendly
    • 1
      Good use of the great couchDb and offline first
    CONS OF HOODIE
      Be the first to leave a con

      related Hoodie posts

      LokiJS logo

      LokiJS

      23
      39
      2
      In-memory JavaScript Datastore with Persistence
      23
      39
      + 1
      2
      PROS OF LOKIJS
      • 2
        Can query the objects directly
      CONS OF LOKIJS
        Be the first to leave a con

        related LokiJS posts

        Couchbase logo

        Couchbase

        390
        493
        102
        Document-Oriented NoSQL Database
        390
        493
        + 1
        102
        PROS OF COUCHBASE
        • 18
          High performance
        • 17
          Flexible data model, easy scalability, extremely fast
        • 8
          Mobile app support
        • 6
          You can query it with Ansi-92 SQL
        • 5
          All nodes can be read/write
        • 4
          Local cache capability
        • 4
          Open source, community and enterprise editions
        • 4
          Both a key-value store and document (JSON) db
        • 4
          Equal nodes in cluster, allowing fast, flexible changes
        • 3
          Automatic configuration of sharding
        • 3
          SDKs in popular programming languages
        • 3
          Elasticsearch connector
        • 3
          Easy setup
        • 3
          Web based management, query and monitoring panel
        • 3
          Linearly scalable, useful to large number of tps
        • 3
          Easy cluster administration
        • 3
          Cross data center replication
        • 2
          NoSQL
        • 2
          DBaaS available
        • 2
          Map reduce views
        • 1
          FTS + SQL together
        • 1
          Buckets, Scopes, Collections & Documents
        CONS OF COUCHBASE
        • 3
          Terrible query language

        related Couchbase posts

        Ilias Mentzelos
        Software Engineer at Plum Fintech · | 9 upvotes · 42.5K views
        Shared insights
        on
        MongoDBMongoDBCouchbaseCouchbase

        Hey, we want to build a referral campaign mechanism that will probably contain millions of records within the next few years. We want fast read access based on IDs or some indexes, and isolation is crucial as some listeners will try to update the same document at the same time. What's your suggestion between Couchbase and MongoDB? Thanks!

        See more
        Gabriel Pa

        We implemented our first large scale EPR application from naologic.com using CouchDB .

        Very fast, replication works great, doesn't consume much RAM, queries are blazing fast but we found a problem: the queries were very hard to write, it took a long time to figure out the API, we had to go and write our own @nodejs library to make it work properly.

        It lost most of its support. Since then, we migrated to Couchbase and the learning curve was steep but all worth it. Memcached indexing out of the box, full text search works great.

        See more
        IndexedDB logo

        IndexedDB

        27
        62
        0
        A low-level API for client-side storage of significant amounts of structured data
        27
        62
        + 1
        0
        PROS OF INDEXEDDB
          Be the first to leave a pro
          CONS OF INDEXEDDB
            Be the first to leave a con

            related IndexedDB posts