Joyent vs. Amazon Web Services

Downtime and latency are revenue killers. Having zero visibility into how and when outages happen is worse. Why expose your mission-critical web applications to these risks? Stop building fixes around cloud services that are inherently unstable. Consider an alternative that is designed for resiliency and stability at its core.

At Joyent, we provide a stack that reliably delivers consistent performance across a wide range of loads and can handle the unpredictable usage patterns of today’s demanding user-intensive apps. We provide a cloud-native architecture that utilizes software-driven techniques to manage compute, storage and networking resources in secure zones. There are fewer points of failure within our design, and persistent storage is not dependent on the network in order to operate.

Joyent Delivers Greater Stability and Performance

Comparison of Joyent and AWS features.

Joyent Cloud: Faults are Isolated

Illustration of Joyent technology stack.

Joyent Cloud: Failures Don't Spread

  1. Zones isolate each application environment
  2. ZFS manages a storage pool of virtualized physical drives, if a physical drive fails ZFS automatically replicates without disruption to the compute node
  3. Thousands of zones can be created on one kernel
  4. Zones virtualize the hardware resources

Everyone's components can fail, but in Joyent's architecture, a failing component only affects the infrastructure that is directly dependent upon that component. For example, if a disk fails, ZFS automatically begins resilvering—with minimal disruption and no downtime to the compute node. If an entire compute node fails, only the virtual machines provisioned on that node fail; other nodes are unaffected. And in the unlikely event of broader failure the affected components stop, but the failure doesn't spread.

Illustration of AWS technology stack.

AWS: Failures Can Debilitate the Entire Cloud

  1. Multiple instances can be hosted on individual machines
  2. Hypervisor virtualizes the hardware resources
  3. Amazon Elastic Compute (EC2) virtualizes hardware to host individual applications
  4. EC2 and EBS connected via network
  5. AWS – Elastic Block Store for persistent storage is abstracted from EC2. It must reside in the same availability zone
  6. Mirroring for scaling and replication – connected via network

In Amazon's EBS architecture, a single failure can leap the fire line that traditionally separates systems: a networking fault or single component failure can debilitate scores of otherwise-unrelated EBS-attached instances. And because many have designed their systems to dynamically provision EBS volumes, EBS provisioning can find itself squarely in the recovery path: if an outage is itself EBS-induced, the time to recovery can be greatly exacerbated by the increase in EBS provisioning load.

Pricing Comparison

Sign up Now For

Instant Cloud Access

Get Started