AWS IoT Device Management helps users register new devices by using the IoT management console or API to upload templates populated with information like device manufacturer and serial number, X.509 identity certificates, or security policies. Users can then configure a fleet of devices with this information with a few clicks in the management console. Device fleets can then be grouped into a hierarchical structure based on function, security requirements, or any other category.
N/A
D2iQ Mesosphere
Score 7.5 out of 10
N/A
D2iQ (formerly Mesosphere) still supports the Mesosphere solution, which is designed for operations at a very large scale. It's powered by DC/OS, a production-proven cloud native platform that runs containers and data services on the same infrastructure.
D2iQ rebranded to reflect their change and broadening of focus towards Kubernetes but other services such as Cassandra, Kafka, and Spark. D2iQ also now offers IT professional services in tandem with its products.
N/A
Pricing
AWS IoT Device Management
D2iQ Mesosphere
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
AWS IoT Device Management
D2iQ Mesosphere
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS IoT Device Management
D2iQ Mesosphere
Considered Both Products
AWS IoT Device Management
No answer on this topic
D2iQ Mesosphere
Verified User
Anonymous
Chose D2iQ Mesosphere
Mesosphere vs. ECS Mesosphere has a direct competition with companies using AWS Cloud, as the ECS product is one of the closest competitors to Mesosphere. Mesosphere has an edge with simplistic hosting and deep and easy integration with Jenkins Pipelines and native plugins …
I happen to like mesosphere because it integrates well with a Jenkins based workflow, Deis is a little more Heroku like and it's not clear how to fit that model into a continuous-integration process. Kubernetes has also been criticized for being complicated.
I think right now Mesosphere is newer to Windows environments and has some challenges with stepping in to big data scenarios where YARN is currently being used.
Setting up is a bit of a hassle, especially ZooKeeper state management and mesos and marathon quorum.
Occasionally, I observed some failures when deploying something onto Marathon. Logging or detailed error reporting can help.
Stale containers and inconsistent states resultant of the cluster failure are hard to solve and need a complete system restart to get it back to normal state.
Mesosphere vs. ECS Mesosphere has a direct competition with companies using AWS Cloud, as the ECS product is one of the closest competitors to Mesosphere. Mesosphere has an edge with simplistic hosting and deep and easy integration with Jenkins Pipelines and native plugins support. ECS, on the other hand, does not have much integration with the continuous integration process and is somewhat complex to maintain and manage.
