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.
SAS Advance Analytics is well suited for data that is visual. Data where you want to see multiple graphs and models are good for this software. However, if your data is more descriptive this may not be the best program. SAS is well suited for data where you need to make comparisons on the feasibility of two different programs. Data that can be compared is perfect for this software.
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.
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.
SAS Analytics does not have very good graphic capabilities. Their advanced graphics packages are expensive, and still not very appealing or intuitive to customize.
SAS Analytics is not as up-to-date when it comes to advanced analytical techniques as R or other open-source analytics packages.
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.
Not only does SAS become easier to use as the user gets more familiar with its capabilities, but the customer service is excellent. Any issues with SAS and their technical team is either contacting the user via email, chat, text, WebEx, or phone. They have power users that have years of experience with SAS there to help with any issue.
If SAS Enterprise Guide is utilized any beginning user will be able to shorten the learning curve. This is allow the user a plethora of basic capabilities until they can utilize coding to expand their needs in manipulating and presenting data. SAS is also dedicated to expanding this environment so it is ever growing.
SAS probably has the most market saturation out of all of the analytics software worldwide. They are in every industry and they are knowledgable about every industry. They are always available to take questions, solve issues, and discuss a company's needs. A company that buys SAS software has a dedicated representative that is there for all of their needs.
Although nothing is perfect, SAS is almost there. The software can handle billions of rows of data without a glitch and runs at a quick pace regardless of what the user wants to perform. SAS products are made to handle data so performance is of their utmost important. The software is created to run things as efficiently as SAS software can to maximize performance.
SAS is generally known for good support that's one of the main reasons to justify the cost of having SAS licenses within our organization is knowing that customer support is just a quick phone call away. I've usually had good experiences with the SAS customer support team it's one of the ways in which the company stands out in my view.
SAS has regional and national conferences that are dedicated to expanding users' knowledge of the software and showing them what changes and additions they are making to the software. There are user groups in most of the major cities that also provide multi-day seminars that focus on specific topics for education. If online training isn't the best way for the user, there is ample in-person training available.
There are online videos, live classes, and resource material which makes training very easy to access. However, nothing is circumstantial so applying your training can get tricky if the user is performing complex tasks. When purchasing software, SAS will also allocate education credits so the user(s) can access classes and material online to help expand their knowledge.
Ask as many questions you can before the install to understand the process. Since a third party does the installation your company is sort of a passanger and it is easy to get lost in the process. It also helps to have all users and IT support involved in the install to help increase the knowledge as to how SAS runs and what it needs to perform correctly.
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
SAS was the incumbent tool, and what the team knew. We did look into using Revolution Analytics enterprise version of R, but the learning curve on that caused us to stick with SAS. In my current position, I've opted for WPS over SAS. I can still leverage my SAS experience, but the price is about 15% of what SAS charges, with extra functionality, such as direct database access. I can supplement WPS with free software, such R for anything that it might be missing.
It all depends on the type of SAS product the user has. Scaleability differs from product to product, and if the user has SAS Office Analytics the scaleability is quite robust. This software will satisfy the majority of the company's analytic needs for years to come. In addition, if SAS is not meeting the users needs the company can easily find SAS solutions that will.
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.
