Making a summary of Q1 2018, Forrester (Dave Bartoletti and John R. Rymer) published its overview of 17 Public Cloud Development Platforms currently presented at the market. The core purpose is to present dynamically changing vendors landscape and simplify the platform choice for companies worldwide.
As stated in the report, software developers are actively choosing cloud platforms due to three main reasons:
- Improve productivity via automation and infrastructure abstraction
- Speed time-to-market for customer-facing applications
- Leverage cutting-edge technologies
Forrester predicts that more than 50% of global enterprises will rely on at least one public cloud platform to drive digital transformation and satisfy customers.
Current choice of cloud providers can be sorted at least by two criteria:
- Size: large (more than $1billion in annual revenue), midsize ($250 million to $1 billion), and small (less than $250 million) providers
- Functional segments: full-stack, development-only, low-code platforms
In this overview Forrester listed Jelastic along with AWS, Microsoft Azure and Google Cloud as a full-stack cloud platform provider. It is mentioned that such type of platforms gives developers deep control over their application architectures, offers runtimes for projects written in various languages, DevOps toolchains, Containers-as-a-Service (CaaS), database and analytics services, and many more.
Jelastic provides turnkey multi-cloud Platform-as-a-Service for developers across data centers from local service providers worldwide. The company accumulated the required knowledge related to routine and complex infrastructure management tasks and incorporated automation within simple and intuitive UI backed by powerful orchestration platform.
In addition, Jelastic keeps accomplishing the stated objective to solve inefficiency of current cloud resource usage. For this, there was introduced elastic vertical scaling with containers and “pay as you use” billing model based on the real usage, not on the limits of a VM. So developers can set high limits for scaling but if resources are not used no charges are done. It solves so-called “right sizing” problem (when you need to guess what VM size is required) and eliminates overpaying in general.