Oracle Autonomous Data Warehouse is optimized for analytic workloads, including data marts, data warehouses, data lakes, and data lakehouses. With Autonomous Data Warehouse, data scientists, business analysts, and nonexperts can discover business insights using data of any size and type. The solution is built for the cloud and optimized using Oracle Exadata.
Apache Cassandra is a NoSQL database and well suited where you need highly available, linearly scalable, tunable consistency and high performance across varying workloads. It has worked well for our use cases, and I shared my experiences to use it effectively at the last Cassandra summit! http://bit.ly/1Ok56TK It is a NoSQL database, finally you can tune it to be strongly consistent and successfully use it as such. However those are not usual patterns, as you negotiate on latency. It works well if you require that. If your use case needs strongly consistent environments with semantics of a relational database or if the use case needs a data warehouse, or if you need NoSQL with ACID transactions, Apache Cassandra may not be the optimum choice.
II would recommend Oracle Autonomous Data Warehouse to someone looking to fully automate the transferring of data especially in a warehouse scenario though I can see the elasticity of the suite that is offered and can see it is applicable in other scenarios not just warehouses.
Continuous availability: as a fully distributed database (no master nodes), we can update nodes with rolling restarts and accommodate minor outages without impacting our customer services.
Linear scalability: for every unit of compute that you add, you get an equivalent unit of capacity. The same application can scale from a single developer's laptop to a web-scale service with billions of rows in a table.
Amazing performance: if you design your data model correctly, bearing in mind the queries you need to answer, you can get answers in milliseconds.
Time-series data: Cassandra excels at recording, processing, and retrieving time-series data. It's a simple matter to version everything and simply record what happens, rather than going back and editing things. Then, you can compute things from the recorded history.
Very easy and fast to load data into the Oracle Autonomous Data Warehouse
Exceptionally fast retrieval of data joining 100 million row table with a billion row table plus the size of the database was reduced by a factor of 10 due to how Oracle store[s] and organise[s] data and indexes.
Flexibility with scaling up and down CPU on the fly when needed, and just stop it when not needed so you don't get charged when it is not running.
It is always patched and always available and you can add storage dynamically as you need it.
Cassandra runs on the JVM and therefor may require a lot of GC tuning for read/write intensive applications.
Requires manual periodic maintenance - for example it is recommended to run a cleanup on a regular basis.
There are a lot of knobs and buttons to configure the system. For many cases the default configuration will be sufficient, but if its not - you will need significant ramp up on the inner workings of Cassandra in order to effectively tune it.
It is very expensive product. But not to mention, there's good reasons why it is expensive.
The product should support more cloud based services. When we made the decision to buy the product (which was 20 years ago,) there was no such thing to consider, but moving to a cloud based data warehouse may promise more scalability, agility, and cost reduction. The new version of Data Warehouse came out on the way, but it looks a bit behind compared to other competitors.
Our healthcare data consists of 30% coded data (such as ICD 10 / SNOMED C,T) but the rests is narrative (such as clinical notes.). Oracle is the best for warehousing standardized data, but not a good choice when considering unstructured data, or a mix of the two.
I would recommend Cassandra DB to those who know their use case very well, as well as know how they are going to store and retrieve data. If you need a guarantee in data storage and retrieval, and a DB that can be linearly grown by adding nodes across availability zones and regions, then this is the database you should choose.
Does not require continous attention from the DBA, autonomous features allows the database to perform most of the regular admin tasks without need for human intervention.
Allows to integrate multiple data sources on a central data warehouse, and explode the information stored with different analytic and reporting tools.
Understanding Oracle Cloud Infrastructure is really simple, and Autonomous databases are even more. Using shared or dedicated infrastructure is one of the few things you need to consider at the moment of starting provisioning your Oracle Autonomous Data Warehouse.
We evaluated MongoDB also, but don't like the single point failure possibility. The HBase coupled us too tightly to the Hadoop world while we prefer more technical flexibility. Also HBase is designed for "cold"/old historical data lake use cases and is not typically used for web and mobile applications due to its performance concern. Cassandra, by contrast, offers the availability and performance necessary for developing highly available applications. Furthermore, the Hadoop technology stack is typically deployed in a single location, while in the big international enterprise context, we demand the feasibility for deployment across countries and continents, hence finally we are favor of Cassandra
As I mentioned, I have also worked with Amazon Redshift, but it is not as versatile as Oracle Autonomous Data Warehouse and does not provide a large variety of products. Oracle Autonomous Data Warehouse is also more reliable than Amazon Redshift, hence why I have chosen it
I have no experience with this but from the blogs and news what I believe is that in businesses where there is high demand for scalability, Cassandra is a good choice to go for.
Since it works on CQL, it is quite familiar with SQL in understanding therefore it does not prevent a new employee to start in learning and having the Cassandra experience at an industrial level.
Overall the business objective of all of our clients have been met positively with Oracle Data Warehouse. All of the required analysis the users were able to successfully carry out using the warehouse data.
Using a 3-tier architecture with the Oracle Data Warehouse at the back end the mid-tier has been integrated well. This is big plus in providing the necessary tools for end users of the data warehouse to carry out their analysis.
All of the various BI products (OBIEE, Cognos, etc.) are able to use and exploit the various analytic built-in functionalities of the Oracle Data Warehouse.
