What users are saying about

ThingWorx

6 Ratings

Amazon Web Services

308 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.7 out of 101

ThingWorx

6 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 9.1 out of 101

Add comparison

Likelihood to Recommend

Amazon Web Services

AWS is a very scalable Platform as a Service (PaaS) -- making it usefull for all sizes. With AWS the failover model can be complicated in terms of selecting the right option for you. Failover within a distribution center is one level, while zone level fail over is a larger one. Be sure to understand your capability needs and discuss with AWS these different choices.
No photo available

ThingWorx

Using for device tracking on the shopfloor and event monitoring:- Smooth deployment, easy to couple to devices.- Easy cooperation with splunk, that we use also.- Finally after connecting to deviced (machine data logs), quick definition and implementation of application- Intuitive environment, easy querying.- Can handle virtually any data type we found.- And it works in cloud - a major benefit in our setup.
Viktor Mulac profile photo

Feature Rating Comparison

Infrastructure-as-a-Service (IaaS)

Amazon Web Services
8.3
ThingWorx
Service-level Agreement (SLA) uptime
Amazon Web Services
8.7
ThingWorx
Dynamic scaling
Amazon Web Services
8.9
ThingWorx
Elastic load balancing
Amazon Web Services
9.0
ThingWorx
Pre-configured templates
Amazon Web Services
7.7
ThingWorx
Monitoring tools
Amazon Web Services
7.9
ThingWorx
Pre-defined machine images
Amazon Web Services
7.9
ThingWorx
Operating system support
Amazon Web Services
8.5
ThingWorx
Security controls
Amazon Web Services
8.2
ThingWorx

Pros

  • AWS constantly innovates and iterates, announcing new features several times per year. Earlier this year, for example, they introduced provisioned IOPS for EBS, suddenly providing us with an inexpensive solution to a performance quandary we'd been facing.
  • AWS has provided us with access to the product owners and architects of the products we use most. In turn, those resources provided us with visibility into the product road maps. This enabled us to improve our long-term infrastructure planning, and avoid expensive features that we'd get for free later in the year.
  • AWS peremptorily lowers costs a couple of times per year. This has helped us keep our bill reasonable even as we consume more and more of the AWS services. We periodically compare the cost of AWS to the cost of moving into our colo, and every year the colo looks less and less attractive.
Marc Schriftman profile photo
  • Aggregation of data from production controllers
  • Drill down to details on a one device level
  • Quick monitoring of extraordinary behavior of a monitored component
Viktor Mulac profile photo

Cons

  • Occasionally, we disagree with their roadmap priorities. For example, we really needed Content-Based Routing added to ELB to support our multitenant implementation. The AWS architects agreed that it was a mainstream, valuable request and hinted that they were trying to get it onto the roadmap, but 15 months later there's still no sign of it. I'm sure they have their reasons, but it's a strange and annoying hole in an otherwise invaluable service.
  • AWS has had well-publicized outages that have broken the promise of true zone (datacenter) isolation. This was supposed to have been impossible - if you had instances running in two zones within a region, you thought had a solid survivability story. We were forced to react by building out additional redundancy that increased costs beyond our original design estimates. AWS claims to have resolved the problem, but we haven't been confident enough to spin down the extra servers yet.
  • There are annoying resource limits, presumably in place to prevent hackers from allocating huge numbers of resources on a compromised account. The problem is that raising the resource limits requires manual action to be taken, and can have a severe impact on production software if your ops team isn't meticulous in checking the limits. As of the last time I checked, these limits weren't available via API, making it impossible to create alarms whenever we get close to exceeding our resource limits.
  • AWS is relatively infamous for their poor communications during outages. Their status page will occasionally go without an update for 45 minutes, while half your customers are dead in the water. This is - obviously - infuriating.
Marc Schriftman profile photo
  • Until now can not think of any. Data acquisition was a problem initially - solved by connection server and splunk.
Viktor Mulac profile photo

Likelihood to Renew

Amazon Web Services9.4
Based on 10 answers
We are almost entirely satisfied with the service. In order to move off it, we'd have to build for ourselves many of the services that AWS provides and the cost would be prohibitive. Although there are cost savings and security benefits to returning to the colo facility, we could never afford to do it, and we'd hate to give up the innovation and constant cycle of new features that AWS gives us.
Marc Schriftman profile photo
ThingWorx10.0
Based on 1 answer
We started more than a year ago and do not plan to replace it
Viktor Mulac profile photo

Usability

Amazon Web Services9.0
Based on 3 answers
The management console is the weak part of the service in my experience. It is adequate but slow.
No photo available
No score
No answers yet
No answers on this topic

Reliability and Availability

Amazon Web Services9.0
Based on 1 answer
Availability is very good, with the exception of occasional spectacular outages.
No photo available
No score
No answers yet
No answers on this topic

Performance

AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.
No photo available
No answers on this topic

Support

Amazon Web Services3.0
Based on 3 answers
Neutral, no experience with either.
No photo available
No score
No answers yet
No answers on this topic

Implementation

Amazon Web Services10.0
Based on 3 answers
The API's were very well documented and was Janova's main point of entry into the services.
Brian Lusenhop profile photo
No score
No answers yet
No answers on this topic

Alternatives Considered

We also looked at Rackspace but was attracted to AWS by the breadth of services available at comparable cost and reliability.
No photo available
E.g. splunk and SAB BO, currently also Power BIOther areas: Blockchain development - Ethereum (EVM) on Solidity
Viktor Mulac profile photo

Return on Investment

  • It would be difficult to quantify the ROI exactly, but it virtually eliminates capital expenditures on hardware and at least halves the need for IT labor.
No photo available
  • Our v-business is built on ThingWorx
  • High impact.
Laurie Reynolds profile photo

Pricing Details

Amazon Web Services

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details

ThingWorx

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details