Apache CouchDB is an HTTP + JSON document database with Map Reduce views and bi-directional replication. The Couch Replication Protocol is implemented in a variety of projects and products that span computing environments from globally distributed server-clusters, over mobile phones to web browsers.
Great for REST API development, if you want a small, fast server that will send and receive JSON structures, CouchDB is hard to beat. Not great for enterprise-level relational database querying (no kidding). While by definition, document-oriented databases are not relational, porting or migrating from relational, and using CouchDB as a backend is probably not a wise move as it's reliable, but It may not always be highly available.
If you have a cluster of nodes with MariaDB MaxScale and you want all the nodes of the cluster to have a similar load and not to be be penalized for queries or writes to the database, you can mount the MaxScale product in front of the MariaDB cluster. MaxScale will balance the requests based on what is being sent to each node to have an equitable load and will cache the queries that it sends to each one. This optimizes the response time to database queries and spreads the load out among all nodes in a similar way.
It can replicate and sync with web browsers via PouchDB. This lets you keep a synced copy of your database on the client-side, which offers much faster data access than continuous HTTP requests would allow, and enables offline usage.
Simple Map/Reduce support. The M/R system lets you process terabytes of documents in parallel, save the results, and only need to reprocess documents that have changed on subsequent updates. While not as powerful as Hadoop, it is an easy to use query system that's hard to screw up.
Sharding and Clustering support. As of CouchDB 2.0, it supports clustering and sharding of documents between instances without needing a load balancer to determine where requests should go.
Master to Master replication lets you clone, continuously backup, and listen for changes through the replication protocol, even over unreliable WAN links.
Because our current solution S3 is working great and CouchDB was a nightmare. The worst is that at first, it seemed fine until we filled it with tons of data and then started to create views and actually delete.
Couchdb is very simple to use and the features are also reduced but well implemented. In order to use it the way its designed, the ui is adequate and easy. Of course, there are some other task that can't be performed through the admin ui but the minimalistic design allows you to use external libraries to develop custom scripts
MariaDB MaxScale is a powerful tool and easy to use. It has helped us a lot to improve the performance of our database queries. It implements a security layer that acts as a firewall for the databases, masks the data, or limits the results of the queries. It also integrates easily with Kafka.
We have launched several inquiries to MariaDB MaxScale support, and they have always responded very quickly. They also want to hold frequent meetings with the client to get their opinion understand how they can help. I see a very human support that is concerned about the customer.
it support is minimal also hw requirements. Also for development, we can have databases replicated everywhere and the replication is automagical. once you set up the security and the rules for replication, you are ready to go. The absence of a model let you build your app the way you want it
ProxySLQ allows many simultaneous connections and allows the cache of queries in memory but it does not have high availability or scalability natively, only through external tools. HAProxy is not able to perform load balancing in an optimal way.
Instead, MariaDB MaxScale allows high availability, scalability, and data replication to external systems such as Kafka. In addition, MaxScale has a monitor that allows you to see the status of the set of databases.
