gartner magic quadrant

Download Gartner Magic Quadrant

Post on 03-Aug-2015

791 views

Category:

Documents

2 download

Embed Size (px)

TRANSCRIPT

1. G00270939 Magic Quadrant for Enterprise Integration Platform as a Service, Worldwide Published: 23 March 2015 Analyst(s): Massimo Pezzini, Yefim V. Natis, Paolo Malinverno, Kimihiko Iijima, Jess Thompson, Eric Thoo, Keith Guttridge Initially focused on point-to-point integration across cloud and on-premises applications, enterprise iPaaS offerings can now effectively target more- complex uses. This Magic Quadrant helps directors of integration assess providers' ability to deliver offerings that meet current and evolving needs. Strategic Planning Assumptions By 2017, in large organizations, at least 65% of new integration flows will be developed outside the control of IT departments. By 2018, the iPaaS market will further fragment, with no vendor exceeding 15% of the global iPaaS customer base. Market Definition/Description Integration platform as a service (iPaaS) is a cloud service that provides a platform to support application, data and process integration projects, usually involving a combination of cloud-based applications, APIs and on-premises systems. iPaaS delivers some combination of capabilities that are typically found in enterprise service buses (ESBs), data integration tools, B2B gateways, managed file transfer products and API management platforms. IT departments, line of business (LOB) developers, mobile application development (AD) teams, application teams and even business users (aka "citizen integrators") leverage these capabilities to develop, execute and manage integration interfaces (or "integration flows") in the cloud. iPaaS Functionality iPaaS functionality typically includes: Support for (and bridging between) a variety of connectivity protocols and data/message delivery styles Data/message mapping and transformation 2. Data quality Routing and orchestration Adapters for cloud-based and on-premises applications, data sources and technology environments On-premises software agents to enable secure communication between on-premises systems and the iPaaS environment Adapter developer toolkits Integration flow development and life cycle management tools Integration flow management, administration and monitoring API management Reusable integration templates Prepackaged integration flows ("cloudstreams") As discussed in the Inclusion and Exclusion Criteria paragraph, not all of these capabilities are required for a cloud service to qualify as an iPaaS. At this stage, some of them are considered as helpful optional capabilities (for example, data quality, API management, adapter developer toolkits and cloudstreams), even if they may become more relevant as market demand evolves. Although the functionality of an iPaaS is implemented by the provider through software technology, the ultimate iPaaS deliverable is a cloud service, not a software product. Therefore, this Magic Quadrant considers only companies that provide integration platforms in the form of public cloud services, not as software products for on-premises deployments. However, the ability to deliver iPaaS functionality also in the form of equivalent on-premises middleware products is a capability that buyers increasingly require and will likely become a necessary feature to compete in this market. iPaaS Use Cases and Buying Centers The most frequent use case for iPaaS is still what Gartner refers to as "cloud service integration" (CSI), which is the problem of integrating a combination of on-premises applications and data, SaaS applications, and other cloud services (see "What IT Leaders Need to Know About Cloud Services Integration: Proactively Address the Challenge"). However, over the past 12 months, use of iPaaS offerings to support scenarios such as B2B integration, API publishing and management, and mobile app integration (MAI) has notably expanded. Similarly, use of iPaaS offerings in the context of certain types of on-premises integration projects has grown, and some examples of iPaaS use in Internet of Things (IoT) initiatives have also been manifested, albeit still rather sporadically. Therefore, iPaaS is more and more perceived by user organizations as a versatile option that can address a variety of use cases and not just as a point solution for specific issues. Because of their historical characteristics of ease of use and rapid integration enablement, iPaaS offerings tend to be used to support integration issues requiring an adaptive approach focused on short time to deployment. iPaaS offerings are less commonly used in traditional systematic Page 2 of 41 Gartner, Inc. | G00270939 3. integration that focuses on enterprise consistency, quality of service (QoS) and long-term maintainability (see "Adopt an Adaptive Approach to Effectively Support Rapid Integration Requirements"). iPaaS characteristics also match small and midsize businesses' (SMBs') integration requirements. Therefore, iPaaS is currently a prevalent option for this market. In large organizations, iPaaS characteristics fit well with CSI or MAI projects where the use of a high-end, on-premises integration platform, even if already in place, would not be easy to justify, for reasons such as time to integration, cost of entry, deployment complexity, lack of local skills, and lack of adapters for specific SaaS applications. These organizations leverage iPaaS for LOB, subsidiary and/or departmental projects, often in "Mode 2" initiatives in the context of bimodal IT strategies. However, in a growing number of cases, the iPaaS role is being elevated to more strategic, "enterprisewide" relevance in the wake of "cloud first/mobile first" or digital business strategies, often in "Mode 1" projects framed in bimodal IT strategies (see "New Integration Strategies and Technologies Target the Digital Business"). This implies that in large organizations, iPaaS buyers often are not necessarily central IT departments (typically through the enterprise integration competency center [ICC]). They can be LOB managers, subsidiary directors or leaders of other decentralized organizational entities engaged in IT projects not under the control of the central IT department. In some cases, even individuals not necessarily IT professionals working for some form of IT department turn to iPaaS to address simple, often one-off personal integration issues (for example, loading Twitter feeds into Google Docs spreadsheets), thus assuming the role of "citizen integrators" (see "Embrace the Citizen Integrator Approach to Improve Business Users' Productivity and Agility"). However, as iPaaS ascends to a more strategic role, central IT departments are increasingly being involved in iPaaS purchasing decisions, and in a growing number of cases, ICCs are proactively defining iPaaS strategies to anticipate LOBs', application teams' and business users' requirements for adaptive integration. This often leads ICCs toward combining iPaaS offerings with their established on-premises integration platforms in what Gartner calls hybrid integration platforms (see "Why There's a Move Toward Hybrid Integration Platforms" and "How to Use Hybrid Integration Platforms Effectively"). This trend also often implies that ICCs redefine their role from "integration factory" toward "integration facilitator" for do-it-yourself integration requirements (see "The Integrator's Dilemma: Can a Bimodal Approach Balance Integration Agility and Control?"). This will likely determine an evolution of iPaaS offerings toward more extensive support for hybrid, distributed cloud/on- premises deployment models and greater focus by ICCs on regaining control of the organizations' iPaaS strategies. Most iPaaS providers target enterprise requirements (for example, integration between Salesforce and SAP ERP). Some players (for example, CloudWork, elastic.io, IFTTT, Kevy, OneSaas, Zapier) instead concentrate on serving citizen integrators' needs. In this Magic Quadrant, we consider only iPaaS providers targeting enterprise integration challenges hence, we call it Magic Quadrant for Enterprise iPaaS. Gartner, Inc. | G00270939 Page 3 of 41 4. However, many iPaaS vendors are planning to add citizen integrator capabilities to their offerings. Therefore, in the future, the distinction between these two classes of providers may blur. Consequently, they may enter in more-pronounced competition than today, especially in the midsize/large-organization and large-organization segments, where enterprise iPaaS may have an edge because of its greater support for on-premises applications and for central IT/ICC requirements. iPaaS Market Trends The iPaaS market is poised to dramatically grow over the next five years because of several factors, including: The explosion of CSI, MAI, API and IoT requirements The emergence of the adaptive integration approach and citizen integrators for whom traditional integration platforms are generally unsuitable Adoption by SMBs that so far have often been unwilling to embrace integration middleware because of its high cost and complexity, but are now interested in iPaaS offerings due to their low entry cost and ease of use Entry in the market of megavendors and influential software players that can deploy powerful marketing and sales machines to sustain their iPaaS ambitions This expected growth and increasingly strategic relevance of iPaaS have attracted investments from startup companies, megavendors, established on-premises middleware players, providers of other forms of platform as a service (PaaS), and SaaS players. All these vendors are eager to get their fair share of this new, fast-growing market and, most importantly, to establish control in user organizations' crucially strategic next-generation integration infrastructure. This is increasingly leading to an overcrowded and confusing market where competition will be fierce and providers will struggle for awareness. During the past 12 months, the net number of players in the market has grown considerably. Currently, Gartne

Recommended

View more >