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
2. Experience the automated Cloud
Cloud Services
Public
35 datacenters in 25
countries
-
Private On-premise and VPC
Hybrid
Within any clouds (AWS,
Azure, IBM, etc.)
Supported
3. Experience the automated Cloud
Supported Languages
Java, JavaEE, PHP, Ruby, Node.js, Python, Perl
.NET (Native) .NET (Linux based)
5. Java Support
Application Servers
Tomcat, TomEE, Jboss, Jetty,
Glassfish, Wildfly
Tomcat, JBoss, Wildfly, Vert.x
Java Versions 6,7,8 6,7
JEE support Java EE6 and Java EE7
Cloudjiffy supports automatic session replication for Tomcat, GlassFish and Jetty. Also it
automatically configures load balancing if HA for application servers is enabled.
OpenShift provides session replication for JBoss. Also it's possible to add Memcached from
Marketplace and configure session replication manually.
6. Experience the automated Cloud
PHP Support
Application Servers Nginx + FPM, Apache 2 + mod_php
Apache. Zend Server and Nginx
via cartridge
PHP Versions 5.3, 5.4, 5.5, 5.6 5.5
Supported Frameworks
Zend, Yii, Composer, Drush, Phalcon,
Symfony, Cake PHP
CodeIgniter, Laravel, Symfony,
Simple PHP Framework, Cake
PHP
Zero Downtime
Deployment
Supported
7. Experience the automated Cloud
Ruby Support
Application Servers
Nginx + Passenger, Apache +
mod_ruby
Apache + mod_ruby
Ruby Versions
2.2.2, 2.0.0, 2.1.5, 1.9.3.
Switching versions in runtime via
RVM
1.8, 1.9, and 2.0
Dependency
Management
Bundler
Supported Frameworks Rails and Sinatra
8. Docker Support
Available in versions Public, Private, Hybrid Since version 3.0
Docker orchestrator
Cloudjiffy
Orchestrator
Kubernetes
Docker containers redeploy (update) Yes
Live migration Yes No
Support of stateful, stateless and legacy applications All
Stateful and stateless
are supported.
Legacy - partially
UI management of Docker deployment and config files Yes No
CLI management of Docker deployment Yes
Persistent storage Yes
Support of private registries Yes
Volumes to save data during redeployment Yes
9. Experience the automated Cloud
Cloudjiffy DevOps Portals
● Self service portal for developers
● Functional and easy platform
management
10. Experience the automated Cloud
OpenShift Portals
● Self service portal for developers
● Functional and easy platform
management
11. Experience the automated Cloud
Management
Dev and Ops self-service
portals
Advanced Limited
SSH access SSH, SFTP
CLI Client Yes
API
REST API, High level API that
provides ability to create complex
environments
REST API
12. Experience the automated Cloud
Deployment Process
Binary deployment packages war, ear, zip, tar, tar.gz
Possible, but requires manual
configuration
Deployment via VCS GIT/SVN, build on commit GIT
Deployment via plugins for
IDEs
IntelliJ IDEA, Eclipse, NetBeans
Zero Downtime re-deployment
/ rolling updates
for all runtimes
13. Experience the automated Cloud
Scaling
Vertical scaling
(within single HW machine)
Automatic within predefined
limits
-
Horizontal scaling
(across different HW
machines)
Manual and automatic.
Automatic scaling is based on
load triggers: RAM, CPU, I/O,
IOPS, Traffic
Manual - by changing Label
parameter in Kubernetes
Automatic is based on CPU
loading only
14. Experience the automated Cloud
High Availability: Application Level
Shared Load Balancer
Distribution of load balancers on
different hardware nodes to
eliminate risks of single point of
failure
HAProxy is the only server for
Load Balancing
Dedicated Load Balancer
Ability to create via UI dedicated load
balancers with replication and tune
them anyway you want
It is possible to perform HA on
Load Balancing layer but it
requires manual configuration
Application Servers
Scaling and distributing app servers
across hardware cluster along with
configuration of session replication
Scaling app servers along with
support of sticky sessions
Databases
Clustered (master-slave, master-
master, replica set)
-
15. 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
Distribution of nodes inside a
cluster to eliminate risk of
hardware failure
Across Clouds
Can be deployed on bare metal and on
any infrastructure of vCloud (like Azure,
SoftLayer, OVH, AWS), HA can be
configured across different hosts
HA should be provided by
underlying IaaS platform
16.
17. Main Differences
Automatic vertical scaling without downtime Impossible to scale vertically
All Cloudjiffy versions are compatible OpenShift v2 and v3 are incompatible
Possible to choose between 4 LB servers, scale them horizontally and
vertically, provide LB between instances via UI
It is possible to perform HA on Load Balancing layer but it requires
manual configuration via CLI
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
Possible to migrate without downtime inside of cluster, even
between AWS, SoftLayer, Azure, etc.
Impossible to perform live migration of containers
Needs backup-as-a-service for end-users Easy backup and restore via CLI for end-users
Cloudjiffy grants possibility to run and orchestrate Dockers by usual
Enterprise-patterns and simple, but very functional UI
Because of orchestrating Dockers by Kubernetes, necessity of
changing app's architecture, employees' education and integrating
new technologies is present
Minimal System requirements for nodes are 8 CPU cores, 16 GB RAM Minimal System requirements for nodes are 1 vCPU and 8 GB RAM
Unused resources are released into the cluster Impossible to idle pods, that aren’t getting any traffic