Posit, formerly RStudio, is a modular data science platform, combining open source and commercial products.
N/A
Spotfire
Score 8.6 out of 10
N/A
Spotfire, formerly known as TIBCO Spotfire, is a visual data science platform that combines visual analytics, data science, and data wrangling, so users can analyze data at-rest and at-scale to solve complex industry-specific problems.
$0.99
Per Hour (Starting)
Pricing
Posit
Spotfire
Editions & Modules
No answers on this topic
Spotfire for Amazon Web Services
$0.99
Per Hour (Starting)
Spotfire Cloud - Consumer
$250/yr
per seat
Spotfire Cloud - Business Author
$650/yr
per seat
Spotfire Cloud - Analyst
$1250/yr
per seat
Spotfire Platform
Please contact Spotfire sales
Spotfire Cloud Enterprise
Please contact Spotfire sales
Offerings
Pricing Offerings
Posit
Spotfire
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
For Enterprise engagements, please contact TIBCO directly for a custom price quote.
RStudio is code based, so in the beginning tools like Spotfire and Tableau have thier advantages since many things are already built in, but in terms of flexibility RStudio will win over the longer term.
The cost of RStudio and RStudio Connect is very reasonable [for a] small …
RStudio is preferable to SPSS and SAS mainly because it is much lower cost to use even having a server license that we pay for the SAS licenses we used to have are too expensive and ultimately we decided to move away from using SAS for our reporting and data modeling needs.
Spotfire is the best application for power users by virtue of its wide variety of visualizations, incorporated analytics, superior data canvas, and ability to integrate code such as R or Python. The learning curve is steeper and the menus are Windows 7 once you are past some …
The latest version of Spotfire enables users to join data without any friction. For example, if the column in one table has different prefixes and/or postfixes, the tool would automatically join the two tables together without causing any potential debugging alarm or issues …
I feel Tableau is more rigid and not flexible compared to Spotfire. I feel that difference while working with retail data that has more than 10 million records. On Tableau, it took almost 10 minutes to open up a report. Whereas Spotfire did this in a minute. Our data is also …
I have not really used it so much...my impression was that Spotfire has a better processing engine for large data, while Tableau delivers a more beautiful display of data.
In my humble opinion, if you are working on something related to Statistics, RStudio is your go-to tool. But if you are looking for something in Machine Learning, look out for Python. The beauty is that there are packages now by which you can write Python/SQL in R. Cross-platform functionality like such makes RStudio way ahead of its competition. A couple of chinks in RStudio armor are very small and can be considered as nagging just for the sake of argument. Other than completely based on programming language, I couldn't find significant drawbacks to using RStudio. It is one of the best free software available in the market at present.
A high level of data integration is available here it supports various data sources and so on. Collaborating features allow users to give access to the dashboard and merge data analytics with other team members. It can meet the demands of both small and large size business enterprises. A customized dashboard and reports are provided to meet the specific needs and get support of extensibility through APIs and customized scripts.
The support is incredibly professional and helpful, and they often go out of their way to help me when something doesn't work.
The one-click publishing from RStudio Connect is absolutely amazing, and I really like the way that it deploys your exact package versions, because otherwise, you can get in a terrible mess.
Python doesn't feel quite as native as R at the moment but I have definitely deployed stuff in R and Python that works beautifully which is really nice indeed.
Python integration is newer and still can be rough, especially with when using virtual environments.
RStudio Connect pricing feels very department focused, not quite an enterprise perspective.
Some of the RStudio packages don't follow conventional development guidelines (API breaking changes with minor version numbers) which can make supporting larger projects over longer timeframes difficult.
The donut chart is I guess a powerful illustrations but I hope it should be done quite simple in Spotfire. But in Spotfire there are lots of steps involve just to build a simple donut chart.
Table calculation (like Row or Column Differences) should be made simple or there should be drag and drop function for Table Calculation. No need for scripting.
Information Link should be changed. If new columns are added to the table just refreshing the data should be able to capture the new column. No need extra step to add column
There is no viable alternative right now. The toolset is good and the functionality is increasing with every release. It is backed by regular releases and ongoing development by the RStudio team. There is good engagement with RStudio directly when support is required. Also there's a strong and growing community of developers who provide additional support and sample code.
-Easy to distribute information throughout the enterprise using the webplayer. -Ad hoc analysis is possible throughout the enterprise using business author in the webplayer or the thick client. -Low level of support needed by IT team. Access interfaces with LDAP and numerous other authentication methods. -Possible to continually extend the platform with JavaScript, R scripts, HTML, and custom extensions. -Ability to standardize data logic through pre-built queries in the Information Designer. Everyone in the enterprise is using the same logic -Tagging and bookmarking data allows for quick sharing of insights. -Integration with numerous data sources... flat files, data bases, big data, images, etc. -Much improved mapping capability. Also includes the ability to apply data points over any image.
I think it's a quick and easy to use tool. The IDE is very intuitive and easy to adapt to. You do not need to learn a lot of things to use this tool. Any programmer and a person with knowledge or R can quick use this tool without issues.
Basic tasks like generating meaningful information from large sets of raw data are very easy. The next step of linking to multiple live data sources and linking those tables and performing on the fly analysis of the imported data is understandably more difficult.
RStudio is very available and cheap to use. It needs to be updated every once in a while, but the updates tend to be quick and they do not hinder my ability to make progress. I have not experienced any RStudio outages, and I have used the application quite a bit for a variety of statistical analyses
Even though, it's a rather stable and predictable tool that's also fast, it does have some bugs and inconsistencies that shut down the system. Depending on the details, it could happen as often as 2-3 times a week, especially during the development period.
Generally, the Spotfire client runs with very good performance. There are factors that could affect performance, but normally has to do with loading large analysis files from the library if the database is located some distance away and your global network is not optimal. Once you have your data table(s) loaded in the client application, usually the application is quite good performance-wise.
Since R is trendy among statisticians, you can find lots of help from the data science/ stats communities. If you need help with anything related to RStudio or R, google it or search on StackOverflow, you might easily find the solution that you are looking for.
Support has been helpful with issues. Support seems to know their product and its capabilities. It would also seem that they have a good sense of the context of the problem; where we are going with this issue and what we want the end outcome to be.
The instructor was very in depth and provided relevant training to business users on how to create visualizations. They showed us how to alter settings and filter views, and provided resources for future questions. However, the instructor failed to cover data sources, connecting to data, etc. While it was helpful to see how users can use the data to create reports, they failed to properly instruct us on how to get the dataset in to begin with. We are still trying to figure out connections to certain databases (we have multiple different types).
The online training is good, provides a good base of knowledge. The video demonstrations were well-done and easy to follow along. Provided exercises are good as well, but I think there could be more challenging exercises. The training has also gone up in price significantly in the last 3 years (in USD, which hurts us even more in Canada), and I'm not sure it is worth the money it now costs (it is worth how much it cost 3 years ago, but not double that.)
The original architecture I created for our implementation had only a particular set of internal business units in mind. Over the years, Spotfire gained in popularity in our company and was being utilized across many more business units. Soon, its usage went beyond what the original architectural implementation could provide. We've since learned about how the product is used by the different teams and are currently in the middle of rolling out a new architecture. I suggest:
Have clearly defined service level agreements with all the teams that will use Spotfire. Your business intelligence group might only need availability during normal working hours, but your production support group might need 24/7 availability. If these groups share one Spotfire server, maintenance of that server might be a problem.
Know the different types of data you will be working with. One group might be working with "public" data while another group might work with sensitive data. Design your Library accordingly and with the proper permissions.
Know the roles of the users of Spotfire. Will there only be a small set of report writers or does everyone have write access to the Library?
ALWAYS add a timestamp prompt to your reports. You don't want multiple users opening a report that will try and pull down millions of rows of data to their local workstations. Another option, of course, is to just hard code a time range in the backing database view (i.e. where activity_date >= sysdate - 90, etc.), but I'd rather educate/train the user base if possible.
This probably goes without saying, but if possible, point to a separate reporting database or a logical standby database. You don't want the company pounding on your primaries and take down your order system.
RStudio was provided as the most customizable. It was also strictly the most feature-rich as far as enabling our organization to script, run, and make use of R open-source packages in our data analysis workstreams. It also provided some support for python, which was useful when we had R heavy code with some python threaded in. Overall we picked Rstudio for the features it provided for our data analysis needs and the ability to interface with our existing resources.
Spotfire is significantly ahead of both products from an ETL and data ingestion capability. Spotfire also has substantially better visualizations than Power BI, and although the native visualizations aren't as flexible in Tableau, Spotfire enables users to create completely custom javascript visaualizations, which neither Tableau or Power BI has. Tableau and Power BI are likely only superior to Spotfire with respect to embedded analysis on a website.
RStudio is very scalable as a product. The issue I have is that it doesn't necessarily fit in nicely with the mainly Microsoft environment that everybody else is using. Having RStudio for us means dedicated servers and recruiting staff who know how to manage the environment. This isn't a fault of the product at all, it's just part of the data science landscape that we all have to put up with. Having said that RStudio is absolutely great for running on low spec servers and there are loads of options to handle concurrency, memory use, etc.
In an enterprise architecture, if Spotfire Advanced Data services(Composite Studio),data marts can be managed optimally and scalability in a data perspective is great. As the web player/consumer is directly proportional to RAM, if the enterprise can handle RAM requirement accomodating fail over mechanisms appropraitely, it is definitely scalable,
Using it for data science in a very big and old company, the most positive impact, from my point of view, has been the ability of spreading data culture across the group. Shortening the path from data to value.
Still it's hard to quantify economic benefits, we are struggling and it's a great point of attention, since splitting out the contribution of the single aspects of a project (and getting the RStudio pie) is complicated.
What is sure is that, in the long run, RStudio is boosting productivity and making the process in which is embedded more efficient (cost reduction).
