I agree with Jeff here. Furthermore, Cassandra should generally be your solution of last resort - if nothing else works out.
In your case I’d try sqlite or leveldb (or rocksdb). > On 18 Oct 2018, at 11:46, Jeff Jirsa <jji...@gmail.com> wrote: > > I can’t think of a situation where I’d choose Cassandra as a database in a > single-host use case (if you’re sure it’ll never be more than one machine). > > -- > Jeff Jirsa > > >> On Oct 18, 2018, at 12:31 PM, Abdelkrim Fitouri <abdou....@gmail.com> wrote: >> >> Hello, >> >> I am wondering if using cassandra as one local database without the cluster >> capabilities has a sens, (i cannot do multi node cluster due to a technical >> constraint) >> >> I have an application with a purpose to store a dynamic number of colones >> on each rows (thing that i cannot do with classical relational database), >> and i don't want to use documents based nosql database to avoid using Json >> marshal and unmarshal treatments... >> >> Does cassandra with only one node and with a well designer model based on >> queries and partition keys can lead to best performance than postgresql ? >> >> Does cassandra have some limitation about the size of data ? about the >> number of partition on a node ? >> >> Thanks for any details or help. >> >> -- >> >> Best Regards. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
