RStudio provides stable and trusted open source tools in a market frequently flooded by trendy and soon-to-be abandoned software
Overall Satisfaction with RStudio
We use RStudio Connect as a publishing platform for R and Python documents, apps, and APIs. It provides us with a professional, clean looking interface to share our work with internal clients and stakeholders. Our usage began within a relatively small team, but the popularity of RStudio Connect and its features saw that usage grow to a broader group of users that spans multiple departments and business units.
- Excellent Documentation
- Well-designed Features
- RStudio Connect could really benefit from containerized environments to enable isolated, reproducible content.
- RStudio Connect's pricing model is a little frustrating at times. Infrequent consumers of content cost the same as heavy users who publish content regularly. This limits our ability to share the work of our data scientists at a reasonable cost. We would much rather pay more for each "publisher" seat and have much cheaper or free "viewer" seats. This would also likely lead to a greater investment in RStudio Connect on our part, as we would be able to expose the platform to more team members and key funding decision makers.
- Making data science content readily accessible on an intuitive platform has made the work we do less mysterious to our clients/stakeholders
- Clients/stakeholders find engaging with the company's data science function more enjoyable since they have greater visibility into our work via RStudio Connect
We use RStudio Connect over Domino for publishing content because it is much more flexible and user friendly. It also "just works" far more often than Domino. RStudio Connect has much better support for API-type content, such as OpenAPI/Swagger documentation. For interactive web apps, RStudio Connect offers the data scientist more controls in a more intuitive interface to manage processes, load balancing, and URL paths. Domino either has 1) no such functionality, 2) an unintuitive interface, or 3) functionality that is only available to administrators.
Do you think Posit delivers good value for the price?
Yes
Are you happy with Posit's feature set?
Yes
Did Posit live up to sales and marketing promises?
Yes
Did implementation of Posit go as expected?
Yes
Would you buy Posit again?
Yes
Using RStudio
100 - The heavy users of RStudio products in our organization are primarily Data Scientists, Product Analysts, and Business Intelligence Analysts. However, each of these groups have stakeholders located in just about every part of the business, and RStudio Connect is the platform we use to share our work with these audiences, resulting in a very wide range of backgrounds that ultimately interact with Connect.
1 - A Linux administrator is necessary to support RStudio Connect. In our case, an experienced Data Scientist (myself) who has a lot of personal experience with Linux provides this support. In addition to Linux knowledge, a support person needs to be familiar with the types of computing challenges that Data Scientists and Analysts face in their day to day work, so that they can properly configure RStudio settings to best fit these needs.
- Scheduling jobs
- Deploying web apps
- Deploying APIs
- Using scheduled RMarkdown documents for data ETL
- Deploying a shiny app dashboard to monitor a competing product's performance
- Deploying product quality APIs
Evaluating RStudio and Competitors
- Product Features
- Product Usability
- Product Reputation
Usability is a very important element of our decision to go with RStudio Connect. Many alternative software offerings are bloating with half-baked and ill-fitting features, often with lots of redundancy (e.g., many ways to do the same thing). Connect provides a single comprehensive and flexible path to accomplishing a task. This allows Data Scientists to focus on their work rather than learning the nuances of an overly complex tool.
If we had to evaluate these products again, we would add an additional criterion to our rubric that captures the ease of deployment across a federated cloud organization. At the time, we were a single team operating in a single AWS account, but the success and adoption of RStudio Connect has seen the incorporation of other teams across our company. These teams have their own AWS accounts with their own permission rule sets. We would now ask: "How easily can we deploy something like RStudio Connect either across these federated accounts or in such a way that content published to Connect can access other AWS accounts while adhering to security best practices?"
RStudio Support
Pros | Cons |
---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
RStudio provides the same level of support for all of its paid offerings, so we did not need to choose whether to pay for support or go it alone.
Yes - When reporting bugs to RStudio the response is swift, as are all responses to support tickets we've opened. In the case of bugs, RStudio has been great at acknowledging the problem, working with us to identify alternatives and workarounds, and ultimately putting the fixes on their development roadmap. They have also been good at communicating the status of any potential fixes.
During an evaluation of RStudio Server Pro (now called Workbench), I opened a support ticket asking about whether an advanced feature described in the Admin documentation could be used to achieve a particular behavior. Not only did RStudio confirm that yes, this could be done, but they also acknowledged the value in using the feature in such a way and even went so far as to provide a working example of how to do it!
Using RStudio
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | None |
- Scheduling reports
- Setting up email notifications
- Configuring content runtimes
- Deploying RStudio onto a cluster
- Identifying environment differences between Connect and the client machine