Unlike the vast majority of hosting services, Jelastic PaaS does not force developers to follow any specific requirements of immutable infrastructure, proprietary runtimes or API to host a project. Such an approach becomes especially substantial when it comes to migrating from virtual machines to containers, decomposition of traditional (so-called legacy) monoliths to microservices, or while moving from one provider to the other.Removing the necessity of application redesign, Jelastic deployment can be easily performed using archives (zip, tar.gz, war, jar, ear), FTPS/SFTP, GIT/SVN with automatic updates right from the dev panel or via integrated plugins for Maven, Eclipse, NetBeans, IntelliJ IDEA. All together, this makes the entry point easier and more seamless, reducing go-to-market time and eliminating vendor lock-in.
Zero code change approach, as well as application and system containers support, provide the ability to run both cloud-native microservices and legacy monolithic applications based on Java, PHP, Ruby, Node.js, Python and Docker.
In addition, deployment and further running of applications inside containers are not going to be restricted after migration from VMs, letting you to:
- Run several services inside a single container
- Use any required node port
- Attach multiple Public IPv4 or IPv6 per container
- Write to local or remote file system
- Access containers via SSH with compatibility to configuration management tools like Chef or Puppet
- Deploy well-known control panels for VPS and shared hosting management (cPanel, Plesk and ISPManager)
- Perform live migration similar to vMotion
- Deploy Docker Engine in the same way you do with VMs
Execute other operations previously implemented within VPS
Also, Jelastic keeps the same IPs and hostnames for each container after any planned or occasional downtime. As a result, you are freed from the necessity to rewrite them in order to let services keep tracking the right connections.