Magic Quadrant for Enterprise Application Platform as a Service, Worldwide

Recommendations

Info

SaaS applications are major drivers of aPaaS adoption in mainstream enterprise IT organizations. ■ Without high-productivity development services for application development and integration, business process management (BPM), and event processing, cloudControl revenue opportunities will be limited to a subset of the market for enterprise PaaS services. Engine Yard Engine Yard is a cloud-based, shared-hardware, high-control aPaaS that uses a dedicated environment for each tenant. The platform supports a limited set of languages and frameworks: Originally focused just on Ruby on Rails, Engine Yard now also supports Java, Node.js and PHP. Each supported environment is a managed and curated infrastructure stack with a configurable composition. Founded in 2006, Engine Yard was a pioneer in the PaaS market. The platform caters to professional developers looking for a low-level platform that hides and automates system administration of an underlying IaaS. (The platform runs on, and Engine Yard resells, AWS, Azure and Verizon Terremark.) For an aPaaS, Engine Yard provides exceptionally deep control of the underlying environment. In fact, the vendor now refers to the platform as a cloud application management platform, rather than aPaaS, indicating a shift in focus from aPaaS to utilitarian service provider. Applications run directly on the host infrastructure, and subscribers have full root access to the virtual servers. For example, subscribers can define custom Chef recipes to configure the servers. The platform supports manual and scheduled scaling, but no dynamic autoscaling. Strengths ■ ■ ■ ■ Engine Yard has over 1,500 Web 2.0 and digital business clients. It provides a solid foundation for DevOps and continuous delivery. It remains the leading aPaaS for Ruby on Rails deployments. Customers cite Engine Yard's responsiveness, support and reliability as key strengths. The vendor's tenant environments have been shown to scale well, and its underlying infrastructure can be extensively customized, which allows for advanced technical control for customers that want it. Engine Yard's transparent pricing model clearly shows costs for the Engine Yard platform versus the underlying IaaS, and this model is more cost-effective for larger customers than the previous model. Customers can now also deploy Engine Yard on their own IaaS environments. Cautions ■ From a business perspective, Engine Yard stumbled in 2013 when it attempted to expand its market to line of business (LOB) clients in traditional corporate accounts. 2014 was a year of change, and the board brought in a new executive team and restructured the company. The vendor is now refocused on its core strength: the developer and DevOps community. As a result, growth opportunities are limited. Page 4 of 45 Gartner, Inc. | G00271188
■ ■ ■ Engine Yard has limited cloud capabilities, particularly in elasticity and sharing. Its sharedhardware model and lack of dynamic autoscaling mean that it is best-suited for environments that benefit most from manual and preplanned approaches to changing capacity. Engine Yard is primarily focused on alleviating subscribers' responsibilities for managing system infrastructure, but not to the point of relinquishing control of those system resources. Although the abstraction level provided does qualify as PaaS, much of the design and many of the use cases for Engine Yard are close to what Gartner calls "IaaS+." The vendor does not provide its own integration, BPM, big data and analytics capabilities, nor does it offer a model-driven, high-productivity cloud platform environment. Those looking for an application platform for LOB levels of productivity or advanced enterprise projects should look elsewhere. Google Google's aPaaS offering is available in the form of Google App Engine (a shared-OS, high-control application platform) and managed virtual machines (VMs) — a somewhat extended technology of App Engine offered in the less restrictive, but also less elastic, shared-hardware format. Google's aPaaS offering supports Java, Python, Go and PHP programming. It is offered colocated with multiple related services, including Google Compute Engine and future Google Container Engine (both IaaS), as well as some xPaaS offerings, such as SQL and NoSQL database management systems (DBMSs), analytics and mobile back-end services. Strengths ■ ■ ■ Google's large installed base (it claims over 20,000 paying customers) consists of many small Web innovators, some very large Web business sites (such as Snapchat and Khan Academy) and a small, but growing number of mainstream enterprise IT organizations. Additionally, Google claims that over 90% of its internal IT is run on App Engine. This diversity in scale and use patterns creates a strong foundation for support of demanding enterprise workloads that also differ in use patterns and demand for quality of service across industries. Google's well-established reputation as a cloud-native service provider and an early platform and big data innovator lends credibility to App Engine and other xPaaS offerings for projects that seek cloud-native efficiency, scalability and agility. Google's aPaaS offering operates on the same worldwide network of data centers as all other Google services, such as Google Search and Google Apps for Work, reassuring its strategic priority to the company. Some of Google's recently added enterprise capabilities (including 99.95% availability SLAs; multiple models for disaster recovery; enterprise-level support, a relational DBMS in addition to high-scale NoSQL; nonintrusive version control; no planned downtime experience for customers; dynamic multimeasure bidirectional autoscaling; application life cycle management; API management; rich security support; cost optimization for workloads of different urgency; event processing; and conversational mode via channels) mitigate the long-standing obstacles to enterprise adoption of Google's aPaaS. Gartner, Inc. | G00271188 Page 5 of 45
Page 1 and 2: G00271188 Magic Quadrant for Enterp
Page 3: geographic coverage and doubled its
Page 7 and 8: available on Bluemix include the co
Page 9 and 10: capabilities include: a variety of
Page 11 and 12: ■ ■ ■ The Mendix approach to
Page 13 and 14: Strengths ■ ■ ■ ■ Strategic
Page 15 and 16: ■ ■ The vendor's PaaS adoption
Page 17 and 18: ■ ■ ■ OutSystems Forge curren
Page 19 and 20: are not interchangeable, however.)
Page 21 and 22: development platform to advance the
Page 23 and 24: lack of standardized disaster recov
Page 25 and 26: ■ ■ ■ Zoho Creator is very "c
Page 27 and 28: ■ ■ Encapsulates the underlying
Page 29 and 30: ■ ■ ■ ■ ■ ■ Self-servic
Page 31 and 32: ■ ■ ■ Software modules (sourc
Page 33 and 34: ■ ■ Exposure and access to near
Page 35 and 36: ■ ■ ■ ■ ■ ■ ■ MVC Sta
Page 37 and 38: Context The enterprise aPaaS market
Page 39 and 40: ■ Target audience (see "What IT L
Page 41 and 42: ■ ■ ■ ■ ■ ■ ■ ■ ■
Page 43 and 44: needs evolve and market dynamics ch
Page 45: GARTNER HEADQUARTERS Corporate Head

Magic Quadrant for Enterprise Application Platform as a Service, Worldwide

Create successful ePaper yourself

Delete template?

Save as template?