ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

licensing: All content tagged as licensing in NoSQL databases and polyglot persistence

Licensing: Could It Be Simpler?

In case you think licensing it’s easy, read this post by Alex Gorbachev explaining how remote mirroring, backup, and cold failover come with their own licensing implications1. My thoughts went from “it’s probably me”, to “this can’t be true”, to “not only will you need an army of people to setup things, but also an army to understand what you need to pay for”.

By the way, I consider licensing as being an important part of the experience of a product. The more complicated it is, the less I feel like trying the product, even if feature-wise it comes close to my requirements.


  1. The post refers to Oracle licensing, but I’d venture to say that you could probably find the same simple licensing system in many other places. 

Original title and link: Licensing: Could It Be Simpler? (NoSQL database©myNoSQL)