Deploy Java, PHP, Ruby, Node.js, Go, .NET, Python and Docker applications with no code changes using GIT, SVN, archives or integrated plugins like Maven, Ant, Eclipse, NetBeans, IntelliJ IDEA CloudJiffy will automatically scale your application containers vertically and horizontally, ensuring you only pay for the resources you consume. No capacity planning or resouce wastage. CloudJiffy uses granular 128MB cloudlets. CloudJiffy dashboard provides intuitive application topology wizard, deployment manager, access to log and config files, team collaboration functionality and integration with CI/CD tools

1. Cloudjiffy vs Amazon ECS

2. Docker Support
Supported Docker versions 1.6 and 1.8
minimum is 1.5.0
latest is 1.11.1
Docker orchestrator Cloudjiffy Orchestrator Custom
Docker containers redeploy (update) Yes
Live migration Yes No
Health checks No Yes, but limited
Support of stateful, stateless and legacy applications Yes No
UI management of Docker deployment and config files Yes No
CLI management of Docker deployment Yes Yes
Docker deployment via Manifest Yes Yes
Possibility to attach Public IPs and ports management Yes No
Support of private registries Yes
Persistent volumes Yes

3. Experience the automated Cloud
Cluster Setup
ECS: To create ECS cluster, you will have to choose one of EC2 instances with
pre-defined parameters first. After it you can start scheduling task-definitions.
Cloudjiffy: Instances’ parameters are flexible and are not templated. You just
have to choose one of Docker images from the Public Private Docker registry
and the rest of work will be performed automatically by Cloudjiffy. The
problem is in necessity of existing container template in the pool.

4. Experience the automated Cloud
Docker Container Registries
ECS uses integrated multi-tenant service called ECR (Elastic Container Registry)
for storing, managing and deployment of Docker Container images. There is no
need to operate own repositories.
Cloudjiffy grants possibility to deploy Docker Container images from public
Docker Hub and Private Registry (Quay.io, etc.), but doesn’t have its own
integrated solution for storing Container images.

5. Experience the automated Cloud
Redeployments
ECS: Redeployment is supported but packages lost might occur during the
process.
Cloudjiffy: Redeployment is also supported. Via traffic distribution add-on it is
possible to transfer all requests to newly cloned environment without any lost
package.

6. Experience the automated Cloud
Persistent Volumes
ECS uses Elastic Block Storage that provides persistent block level storage
volumes. Each EBS volume is automatically replicated within its Availability
Zone to protect owner from component failure. Volumes can be local or
shared.
Cloudjiffy implemented persistent volumes via Virtuozzo Storage product. Each
container is automatically replicated inside a cluster several times to grant
owner a failover-resistant service. Volumes can be local or shared.
Also, Cloudjiffy supports shared storage. End users can mount and use volumes
from the shared storage for several instances.

7. Experience the automated Cloud
Performance
ECS uses native Docker implementation, so horizontal scaling is performed
very fast.
Cloudjiffy uses Docker containers on more secured and isolated virtualization
layer. Horizontal scaling requires a little bit more time, than native
implementation because of platform peculiarities.

8. Experience the automated Cloud
Ports Management and Public IPs
ECS: On ECS, we have to manually make sure the two services don’t use the same
port. We have a single VM so we can only run 1 container that requires port 80.
When we try to run the second one, we won’t be able since we have no VM with
port 80 available. Practically, the amount of instances of all containers, across all
services, that require port X is limited by the number of VMs you have on the
cluster.
Impossible to attach Public IP to each Docker container.
Cloudjiffy: As Cloudjiffy uses Docker containers on another virtualization layer, port
management is performed much accurate by configuring endpoints via UI on the
Shared Resolver.
Public IPs can be attached to any Docker container.

9. Experience the automated Cloud
Logging
ECS: can be configured to use Amazon CloudWatch for the centralized keeping
of log files.
Cloudjiffy: can use Logentries, LogStash and Graylog for for the centralized
management of log files. Log files can be accessible via UI or API.

10. Experience the automated Cloud
Health Checking
ECS: uses Elastic Load Balancer health checks which has three major
limitations:
1. ELB health checks are limited to HTTP/TCP checks.
2. If you want to perform a health check on a service, via a protocol, another
than a TCP port, you won't be able to do it. You have to run an HTTP/TCP
server just to be able to respond to health checks.
3. Even if you have a service which already has an HTTP/TCP server, but does
not need an ELB, you still have to create an ELB and bind it, just to be able to
run a health check on it.
Cloudjiffy: doesn’t provide health checking service yet, but has Load Alerts
based on CPU, RAM, Network and storage (IO, IOPS) usage.

11. Experience the automated Cloud
Lock-In to the Platform
ECS will always be exclusive to AWS. If you build your infrastructure around
ECS and would like to move to another cloud provider in a year, you will have a
hard time.
Cloudjiffy doesn’t restrict your freedom of Cloud Vendor choosing. You can run
your cluster on AWS, Google Cloud, Rackspace, Azure or any hosting provider.

12. Cloudjiffy Dashboard is user-
friendly and very easy to use. All
configuration can be set within a
single topology window.
ECS Dashboard is not intuitive.
To become ECS user, you need
to have a fluent experience
with AWS Dashboard first. For
non-experienced users it
causes confusion.

13. Experience the automated Cloud
Management
Developers’ self-service
portal
Advanced Limited
SSH access SSH, SFTP SSH
CLI Client Yes
API
REST API for managing account
and Docker containers
REST API for managing Docker
containers

14. Experience the automated Cloud
Scaling
Vertical scaling
(within single HW
machine)
Automatic within predefined
limits
Via Docker remote API
Horizontal scaling
(across different HW
machines)
Manual and automatic. Automatic
scaling is based on load triggers:
RAM, CPU, I/O, IOPS, Traffic
Manually via CLI

15. Experience the automated Cloud
High Availability: Application Level
Load Balancer
Highly available distributed load
balancers(Nginx, HAProxy,
Apache) on different hardware
nodes to eliminate risks of single
point of failure.
Elastic Load Balancer Service
Application Servers
Scaling and distributing app
servers across hardware cluster to
eliminate risks of single point of
failure, built-in affinity and anti-
affinity rules.
Horizontal scaling of Docker
containers. Affinity & Anti-affinity
rules aren’t presented.

16. Experience the automated Cloud
High Availability: Hardware Level
Hardware
Live migration. Integration with
software-defined storage for
automatic restore of apps state in
case of hardware failure.
Distribution of containers inside a
cluster to eliminate risk of hard
node failure
Services distribution between
Availability Zones. Elastic Block
Storage provides a persistent
storage for Docker volumes.
Across Clouds
Cloudjiffy can be deployed
simultaneously on bare metal HW
and on any cloud infrastructure
(Azure, SoftLayer, OVH, AWS). HA
can be configured across different
clouds
Not available

17. Main Differences
Automatic vertical scaling without downtime Vertical scaling causes downtime
Automatic horizontal scaling is based on load triggers: RAM, CPU, I/O, IOPS, Traffic Manual horizontal scaling is performed via ECS CLI
Docker containers are running on another virtualization layer for better isolation
and improved functionality
Custom Docker orchestrator grants basic functionality
Horizontal scaling takes much time Horizontal scaling is very fast
Possible to attach public IPv4 to each container Impossible to attach public IPv4 to each container
Improved Docker orchestration from UI Docker orchestration from CLI and via API
Possible to migrate without downtime inside of cluster, even between AWS,
SoftLayer, Azure, etc.
Impossible to perform live migration of Docker containers
Zero-downtime re-deployment via Smart Load Balancer Redeployment causes downtime for end users
Cloudjiffy grants possibility to run and orchestrate Dockers by usual Enterprise-
patterns and simple, but very functional UI
ECS manages and orchestrates native Docker containers via API and CLI
Migration between any clouds and infrastructure without lock-in to the platform Customer is locked-in to the Amazon AWS infrastructure

18. Thank You!
Contact us for more information
info@cloudjiffy.com