A well-suited scenario for using AWS Tensor Flow is when having a project with a geographically dispersed team, a client overseas and large data to use for training. AWS Tensor Flow is less appropriate when working for clients in regions where it hasn't been allowed yet for use. Since smaller clients are in regions where AWS Tensor Flow hasn't been allowed for use, and those clients traditionally don't have enough hardware, this situation deters a wider use of the tool.
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.
Amazon Elastic Compute Cloud (EC2) allows resizable compute capacity in the cloud, providing the necessary elasticity to provide services for both, small and medium-sized businesses.
Tensor Flow allows us to train our models much faster than in our on-premise equipment.
Most of the pre-trained models are easy to adapt to our clients' needs.
SageMaker isn't available in all regions. This is complicated for some clients overseas.
For larger instances, when using a GPU, it takes a while to talk to a customer service representative to ask for a limit increase. Given this, it's recommendable to ask in advance for a limit increase in more expensive and larger cases; otherwise, SageMaker will set the limit to zero by default.
Since the data has to be stored in S3 and copied to training, it doesn't allow to test and debug locally. Therefore, we have to wait a lot to check everything after every trail.
Ability to scale across the company is limited based on the users license, cannot share a dashboard to the general view of the company.
Ability to retain session - not simple method to customize view per user (e.g., once session is ended, the users will return next time to the baseline view).
Ability to enable communication between multiple users - leave notes, tag other users, or share specific view.
There is no other platform that meets our needs. Even if it was terrible we would still use it but fortunately for us it is a very solid project with a great support team. I hope in the future to expand our use and get more licences as well as upgrade to RStudio workbench but for now we are very happy.
For someone who learns how to use the software and picks up on the "language" of R, it's very easy to use. For beginners, it can be hard and might require a course, as well as the appropriate statistical training to understand what packages to use and when
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
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.
Microsoft Azure is better than Amazon Tensor Flow because it provides easier and pre-built capabilities such as Anomaly Detection, Recommendation, and Ranking. AWS is better than IBM Watson ML Studio because it has direct and prebuilt clustering capabilities AWS, like IBM Watson ML Studio, has powerful built-in algorithms, providing a stronger platform when comparing it with MS Azure ML Services and Google ML Engine.
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.
I think that RStudio scales pretty well based on the size of the datasets I'm using. It has multithreading capabilities unlike some other statistical analysis programs which is very useful in cutting down on time. The format of RStudio's syntax also makes it very easy to replicate regardless off the scale of the analysis and data set
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).
