Menu
I'm working on a "real-time" website using Nodejs. Currently, I'm using Redis because I need high performance for read-access. The write accesses are not really significant for my use case.
In addition, Redis does not have a query language for the search. So, I create my indexes manually and I use some unions/intersections/... to find some values.
I think that it will be easier to use MongoDB with a embedded finding system and a ORM-like (Mongoose for example). The problem is that I'm not sure that MongoDB is the best choice for my usecase.
What is your advices about the NoSQL DB that I need ? Redis ? CouchDB ? MongoDB ? Cassandra ? etc.
I repeat: I want to have a real good performance for the read accesses and for the searches (the write accesses are not significant), the simplest possible (orm-like ? finding system ? etc.)
Thanks.
315
- Quora Is a NoSQL database optimized for reads, writes or both? Both. Flat File Reads may be done in large blocks of records (millions of bytes) in 1 READ STATEMENT which accesses the disk drive a single time. Same thing with writes.
There are vendors who are extremely clever at systems programming and can squeeze every bit of performance out of write (and RDBMS engines are actually more mature on that front than NoSQL), but I would say on the whole, the architecture of a database itself plays a bigger role in determining write and read speeds. NoSQL DBA, 7 Years.
aerospike - High Performance DB for Fast Read and Fast Write. No Update or Delete - Stack Overflow High Performance DB for Fast Read and Fast Write. No Update or Delete [closed]
This makes great use of spinning disk drives that have poor seek times, but can do serial writes very quickly. But the downside is that when you do a read, you often need to scan through several versions of an object to get the most recent version to ret In which situations is NoSQL better than relational databases such as SQL?
I believe that redis would be the better solution for the following reasons.
You require fast read access and redis provides the fastest solution since the keys are in memory, if not most.
Although mongodb is easier to query in the general case, your problem domain is narrow and once you decide how you would like to query the data, you can put the correct data structures and indexes in place.
196
I would say that Redis is a good fit for your DB, and you should look at something like Solr or elasticsearch to provide your searching.
26
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
