BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] No-SQL Database Recommendation?
- Subject: [Discuss] No-SQL Database Recommendation?
- From: richard.pieri at gmail.com (Richard Pieri)
- Date: Sat, 10 Jan 2015 21:32:04 -0500
- In-reply-to: <16cdf2d0d2b7662c18dd50d7ad16c10b.squirrel@mail.mohawksoft.com>
- References: <54B188FE.4040409@borg.org> <16cdf2d0d2b7662c18dd50d7ad16c10b.squirrel@mail.mohawksoft.com>
On 1/10/2015 5:39 PM, markw at mohawksoft.com wrote: > Using a free database like PostgreSQL will EASILY handle what you want to do. Indeed. There are only two technical reasons for rejecting relational databases out of hand. Neither of them are in the listed requirements. The first is that your data doesn't fit neatly into table rows. Hospital patient records are my go-to example. Relational databases suck at storing and retrieving this kind of data. Trying to make the data fit into tables anyway is a recipe for disaster. The second is that you need to scale beyond the capacity of the underlying hardware to handle relational queries. This means very large data sets and very complex queries. Relational database performance drops in proportion to data size and query complexity. -- Rich P.
- Follow-Ups:
- [Discuss] No-SQL Database Recommendation?
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- [Discuss] No-SQL Database Recommendation?
- References:
- [Discuss] No-SQL Database Recommendation?
- From: kentborg at borg.org (Kent Borg)
- [Discuss] No-SQL Database Recommendation?
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- [Discuss] No-SQL Database Recommendation?
- Prev by Date: [Discuss] No-SQL Database Recommendation?
- Next by Date: [Discuss] No-SQL Database Recommendation?
- Previous by thread: [Discuss] No-SQL Database Recommendation?
- Next by thread: [Discuss] No-SQL Database Recommendation?
- Index(es):