2 ms·
Frankly speaking, Mongo is probably the worst NoSQL database out there, and it has given bad rep for other NoSQL database which do have their use cases, such Ca
by unscaled 3y ago
Frankly speaking, Mongo is probably the worst NoSQL database out there, and it has given bad rep for other NoSQL database which do have their use cases, such Cassandra, DynamoDB, Couchbase and Redis (yes, let's not forget that Redis is also a NoSQL database, without the hype).
Redis is well-known (and sometimes criticized) for being single-threaded, but managing a connection pool on the client side is still necessary, so my statement is obviously not true for ALL NoSQL databases. But it is at least true for Cassandra and as far as I understand for DynamoDB and Couchbase to some degree.
- winrid 3y agoNo statements will apply to all of anything, just thought I'd clarify since in ten years of working with nosql by large the largest deployments were with Mongo. Bad luck maybe :) There are reactive and non-reactive based SQL dbs too. I know someone at Amazon working on one. You can have state per connection and still use epoll or whatever. Even with NodeJS or Vertx you can open a connection against a worker pool, maintain state for that connection, and it doesn't require thread/process per connection. That's merely an implementation detail (and nice isolation for extensions etc).