AWS Glue is a managed extract, transform, and load (ETL) service designed to make it easy for customers to prepare and load data for analytics. With it, users can create and run an ETL job in the AWS Management Console. Users point AWS Glue to data stored on AWS, and AWS Glue discovers data and stores the associated metadata (e.g. table definition and schema) in the AWS Glue Data Catalog. Once cataloged, data is immediately searchable, queryable, and available for ETL.
$0.44
billed per second, 1 minute minimum
JMP
Score 9.2 out of 10
N/A
JMP® is statistical analysis software with capabilities that span from data access to advanced statistical techniques, with click of a button sharing. The software is interactive and visual, and statistically deep enough to allow users to see and explore data.
When the data which requires ETL has different formats, schema, and volume, this service suits them best. So, when the volume is not consistent (typical use-case of healthcare and online shopping), AWS Glue can be the prime choice. When the data is available in both batch and streaming mode, the developer needs to generate a separate codebase. This increases the source code management efforts. So, prefer to go with Glue when the nature of the data is the same (either batched or streamed).
Many organizations have seen their analytical capabilities, and the results from them, plateau. Of these, we've observed, that most of them didn't appreciate that they could do (even) better. These companies should definitely consider JMP. Any company that is research-based can benefit from accelerating their research, learning more in less time, effort and cost, with JMP's tools. Basically, any organization that is hungry enough for improvement to seek out better ways is suitable for JMP. Those who are happy with their current performance are not likely to consider the changes, though they were not major impediments by our clients, required.
After data cleansing, the team also implemented the best practices for using AWS platform services as a Data Lake, such as job bookmarking for AWS Glue jobs, proper delimiter for the AWS Glue crawlers, partitioning in AWS S3, and transformation to parquet file for compression and faster querying time in Amazon Athena.
Data modernization through combining data from multiple sources into a functioning datasets, rebuilding DW, and resctructuring data sources.
Aims to lessen customer complaints, eliminate manual data extraction requests via SR from different data sources, and Increase accuracy, consistency and speed up reconciliation process.
I've mentioned this earlier, but the licensing agreements are very prohibitive. I work with a company where my role has become less and less doing my own analytics and more and more trying to help other people in that role. As we are bringing more people "up to speed" it's hard to justify licenses for 2-3 people when they aren't full time, Six Sigma black belts just looking at stats all day. A floating license option would make this a no-brainer, since these people could continue their other work and add JMP usage as they grow their skills, but this is not something JMP/SAS has offered.
The GUI interface makes it easier to generate plots and find statistics without having to write code. The JSL scripting is a bit of a steep learning curve but does give you more ability to customize your analysis. Overall, I would recommend JMP as a good product for overall usability.
Amazon responds in good time once the ticket has been generated but needs to generate tickets frequent because very few sample codes are available, and it's not cover all the scenarios.
The helpful tips are great for new users. I am always able to find solutions to a tool I am working with through the hep section. And my area has a users group that meets each quarter to share ideas and view upcoming JMP revisions.
The cataloging of data objects is the best in the case of AWS Glue. We use AWS Glue in all of our data pipelines to sync external and internal data sources and to automatically produce SQL-based ETL based on AWS Glue catalog objects. Integration with Amazon products is the other advantage.
We actually use both JMP and IBM SPSS, but I think JMP's complexity lends itself to more in-depth statistical analyses. SPSS is designed for that as well, but we tend to use it more for quicker analyses, and we have found that JMP is far more powerful.
JMP has resulted in literally millions of dollars in ROI due to identification of correctable errors.
Use of JMP control charts JMP has greatly simplified and improved interpretation of Lean, FMEA, and PDSA type analyses.
Use of JMP has enable the testing and subsequent selection of 'best practices' saving uncounted hours in false starts based on 'collective experience'.
The down side is that JMP is not a 'magic box', one still has to take care in applying the tools properly. Moreover, time-consuming approaches using JMP may still be the 'order of the day', because the service (even power user) is unaware of significant shortcuts available for free on the JMP community website.
