Red Hat Jboss Fuse Compared With Mule Esb Enterprise m5a5e

RED HAT JBOSS FUSE SERVICE WORKS 6 COMPARED WITH MULE ESB ENTERPRISE 3.4 COMPETITIVE REVIEW, APRIL 2014

INTRODUCTION The ability to integrate systems and share data across the enterprise is a common datacenter need that varies in complexity. Red Hat® JBoss® Fuse Service Works is best used with integration projects using service-oriented architecture (SOA) principals. Business use cases associated with SOA projects can benefit from additional capabilities available in the product, such as orchestration and governance. Red Hat JBoss Fuse Service Works expands the integration and enterprise service bus (ESB) capabilities found in Red Hat JBoss Fuse. MuleSoft offers multiple integration products. Two are integration bus offerings for on-premise use: Mule ESB Enterprise Community 1 and Mule ESB Enterprise. Only Mule ESB Enterprise is ed by MuleSoft. It offers significantly more on-premise functionality than Mule ESB Enterprise Community, and is therefore the MuleSoft product discussed in this competitive review. 2

THE RIGHT TECHNOLOGY FOR THE JOB Red Hat JBoss Fuse Service Works is a middleware platform with a rich set of technical capabilities to demanding integration solutions.

Middleware integration solution requirements often vary greatly and can influence the technology used for implementation. Some solutions demand centralized, large-scale architectures that integrate systems using reliable, high-performance networks. Others require the ability to handle data loads efficiently using distributed deployments with more enterprise application integration (EAI) patterns. For EAI use cases, Red Hat recommends Red Hat JBoss Fuse. 3 Red Hat JBoss Fuse Service Works is best used for large-scale integration projects. The product has a business rules engine, complex event processing, integration flows, business process execution language (BPEL) engine, messaging, operations istration and management tools, and other technology suitable to meeting demanding integration use cases. In addition, all the technologies included with a Red Hat JBoss Fuse Service Works subscription are ed by Red Hat.

1 Mule ESB Enterprise Community web page — http://www.mulesoft.org/ 2 Mule ESB Enterprise feature comparison — http://www.mulesoft.com/mule-esb-enterprise 3 See the Red Hat JBoss Fuse product page for more information — http://www.jboss.org/products/fuse facebook.com/redhatinc @redhatnews linkedin.com/company/red-hat

redhat.com

A Mule ESB Enterprise subscription includes both content from the Mule open source community plus third-party technology. In fact, these three important pieces of functionality are provided in Mule ESB Enterprise by bundling JBoss community projects: 1. Business rules and complex event processing Mule ESB Enterprise uses older JBoss community project versions for business rules and BPM functionality. Red Hat JBoss Fuse Service Works provides access and enterprise for business rules and BPM functionality based on code from version 6 of the community projects.

Mule ESB Enterprise provides business rules and complex event processing functionality using the Drools Rules Engine from the JBoss community. Mule bundles the Drools 5.0 libraries with the Mule ESB Enterprise distribution. The current Drools version is 6.0, but the latest version Mule s is 5.0.4 Significant differences between Drools 6.0 and 5.0 are detailed in the Drools 6.0 documentation. 5 Red Hat JBoss Fuse Service Works includes and s Drools 6.0. 2. Business process management Mule ESB Enterprise provides business process management functionality using jBPM from the JBoss community. Mule bundles the jBPM 4.4 libraries with the Mule ESB Enterprise distribution. The current jBPM version is 6.0, but the latest version Mule s is 4.4.6 One of many significant differences between jBPM 4.4 and 6.0 is BPMN 2.0 . BPMN 2.0 is the popular business process modeling standard in use today. JBPM 4.4 process designs are based on jBPM process definition language (jPDL) with no provided for BPMN 2.0. Red Hat JBoss Fuse Service Works s jBPM 6.0. 3. Java Message Service Red Hat JBoss Fuse Service Works includes HornetQ for reliable messaging capabilities. HornetQ implements the Java™ Message Service (JMS) 1.1 specification and provides reliable messaging for the platform. The following features are associated with the JMS 1.1 specification: • Point-to-point messaging • Publish and subscribe messaging • Request and reply messaging • Persistent and non-persistent messages • JMS transactions • XA transactions Mule ESB Enterprise does not include JMS as part of the product packaging. Instead, messaging is provided via a third-party vendor.7 Interaction with several of the Mule-ed messaging platforms uses JMS 1.1.8 To use JMS with Mule ESB Enterprise, you need to have or acquire a JMS provider. Depending on your choice of vendor, this could expose you to additional maintenance and costs in addition to license fees.

4 Drools module documentation — Enterprise http://www.mulesoft.org/documentation/display/current Drools+Module+Reference 5 Drools 6.0 Release Notes — http://docs.jboss.org/drools/release/6.0.1.Final/drools-docs/html/ DroolsReleaseNotesChapter.html#drools.ReleaseNotesDrools.6.0.0 6 Drools module documentation — Enterprise http://www.mulesoft.org/documentation/display/current/Drools+Module+Reference 7 Mule list of ed messaging platforms — http://www.mulesoft.org/documentation/display/current/Compatibility 8 Mule vendor specific configuration for various JMS providers — http://www.mulesoft.org/documentation/display/ current/JMS+Transport+Reference#JMSTransportReference-Vendor-specificConfiguration redhat.com

COMPETITIVE REVIEW  Red Hat JBoss Fuse Service Works 6 compared with Mule ESB Enterprise 3.4

2

MAKING THE TECHNOLOGY WORK TOGETHER Red Hat JBoss Fuse Service Works s service component architecture (SCA).

Providing access to a wide variety of technology can benefit customers when it all works together. Red Hat JBoss Fuse Service Works relies on service component architecture (SCA) to organize and assemble integration project functionality.9 SCA is an open software technology created by major software vendors that provides a model for composing applications that follow service-oriented architecture (SOA) principles. Red Hat JBoss Fuse Service Works developers use SCA composites to create integration solutions. SCA composites define the technology used (components), existing services to access (references), and make the composite accessible to the outside world (bindings). All functionality included with Red Hat JBoss Fuse Service Works can be used with an SCA composite. SCA service components that can be used in Red Hat JBoss Service Works composites include Java, Camel, business process execution language (BPEL), business process modeling notation (BPMN), and rules (which includes complex events). Red Hat JBoss Fuse Service Works provides many connectors for developers to use when interacting with external systems. When creating SCA composites within JBoss Developer Studio, there are 17 bindings available through the graphical interface (GUI). Some of the connectors include: • REST • SOAP • File • JMS • Netty All can be used to connect with external systems (SCA reference) or to make the SCA composite accessible as a service (binding).

Red Hat JBoss Fuse Service Works s using Camel.

Using the Camel binding in Red Hat JBoss Fuse Service Works allows developers to expand connectivity options using Camel components. There are over 125 different Camel components ed by Red Hat JBoss Fuse — which is included with Red Hat JBoss Fuse Service Works. These Camel components can be used for connectivity to integration endpoints. If you need additional connectivity options, Apache Camel documentation details how to write custom components.10 You may also be able to find a Camel component provided by a third party that you could use as an alternative to writing a custom component. Mule ESB Enterprise does not use an open standard like SCA for service solution assembly. Instead, Mule ESB Enterprise uses a proprietary service assembly process. Integration solutions are created as applications that contain flows. Within Mule flows, you find high-level building blocks like message sources, message processors, and endpoints. Those high-level building blocks are broken down into smaller elements such as components, transformers, filters, flow controls, and other building blocks.11

9 Service Component Architecture project — http://www.oasis-opencsa.org/sca 10 Apache Camel documentation, Writing Components — http://camel.apache.org/writing-components.html 11 See Mule ESB Enterprise application architecture documentation for more details — http://www.mulesoft.org/documentation/display/current/Mule+Application+Architecture

redhat.com

COMPETITIVE REVIEW  Red Hat JBoss Fuse Service Works 6 compared with Mule ESB Enterprise 3.4

3

Mule’s proprietary service assembly strategy does have some functional similarities with the SCA open standard. Several Mule proprietary building blocks can be loosely mapped to Red Hat JBoss Fuse Service Works SCA composite building blocks. For example, a flow within a Mule application has some similarities with an SCA composite. A major difference is that each Red Hat JBoss Fuse Service Works SCA composite is deployed independently, while Mule allows multiple flows to be defined within a single application. Having multiple flows within a single application — stored as an XML file — can lead to developer concurrency issues since only one developer can work on a Mule application at a time. Mule offers team development and practices documentation that suggests how to reduce concurrency issues and various types of development and runtime conflicts.12 Another similarity is integration protocols. Red Hat JBoss Fuse Service Works provides multiple connectors for developers to use when exposing an SCA composite as a service, or when connecting with external systems. As mentioned earlier, when creating SCA composites within JBoss Developer Studio there are 17 bindings available that could provide access to the composite or access an external system via a reference. In addition, there are over 125 different Camel components ed by Red Hat JBoss Fuse, expanding connectivity options even further. Custom and third-party components can also be used. All adapters and components included with Red Hat JBoss Fuse Service Works can be used in development, testing, production, or any other environment you deploy to within the limits of your subscription.

Mule ESB Enterprise provides 35 different endpoints pre-installed with a subscription.13 Those transports can be supplemented with MuleSoft AnyPoint Connectors.14 Standard cloud connectors are included with a Mule ESB Enterprise subscription and community cloud connectors “are open source software, though each package may vary depending on the third-party maintainer.” 15 Mule endpoints and connectors can be re-used within a message flow or pre-defined configuration pattern. They can be used to allow a caller to connect to a deployed Mule ESB Enterprise application and allow the application to call other systems as needed. In this sense, they share similarities with the SCA service bindings and component references found in a Red Hat JBoss Service Works SCA composite. Messages received by an integration service typically must be prepared for use by business logic. When you wire SCA components together using Red Hat JBoss Fuse Service Works, data transformation between components is performed transparently for you. The SCA infrastructure automatically injects into the mediation layer at runtime a transformation created using Java, JAXB, JSON, Smooks, or XSLT. Transformations between message content are defined at the composite level. This level abstraction allows for looser coupling of transformation logic than if it was hard wired into or between components.

12 See Mule ESB Enterprise documentation on team development — http://www.mulesoft.org/documentation/display/current/Team+Development+with+Mule 13 Mule available transports documentation — http://www.mulesoft.org/documentation/display/current/Transports+Reference 14 MuleSoft cloud connectors — http://www.mulesoft.com/cloud-connectors-full 15 Mulesoft additional cloud connectors documentation — http://www.mulesoft.org/documentation/display/MULE3STUDIO/Additional+Cloud+Connectors

redhat.com

COMPETITIVE REVIEW  Red Hat JBoss Fuse Service Works 6 compared with Mule ESB Enterprise 3.4

4

With Mule ESB Enterprise, a message received in an integration flow is transformed to prepare the message for further processing by business logic. Transformation takes a message from one format to another. For example, XML string data could be transformed into a Java object. Sometimes, a twostep transformation is required in Mule ESB Enterprise. For example, to convert XML to JSON you might first use an XML to Java object transformer, followed by a Java object to JSON transformer. However, since transformation logic is embedded directly in the application flow, it is tightly coupled with the solution. For example, if the interface for a flow changes, the transformers within the flow also likely need to change. Once an integration message has been received, required business logic can be applied. Often, the required business logic involves routing that can be handled in part or whole using integration patterns. Red Hat JBoss Fuse Service Works includes Apache Camel open source software and out-ofthe-box, standards-based integration patterns. These patterns are based on the book Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf.16 These patterns are the de facto standard for discussing enterprise integration. Nearly 50 different patterns are ed by Red Hat JBoss Fuse Service Works. These patterns are broken down into the following categories: • Message routing (15 patterns) • Messaging endpoints (11 patterns) • Messaging systems (6 patterns) • Messaging channels (5 patterns) • Message transformation (5 patterns) • Message construction (2 patterns) • System management (1 pattern) While Mule ESB Enterprise s some of these same enterprise integration patterns, 30 are missing.17 Those that exist do not always translate easily. Some are a simple 1:1 mapping of Mule object names to enterprise integration style pattern names. For example, the integration style pattern named “Pipes and Filters” is a “flow” Mule object. In other cases, a single integration style pattern name could be multiple Mule object names. For example, aggregator could map to one of 3 Mule objects: collection aggregator, message chunk aggregator, or custom aggregator. Red Hat JBoss Fuse Service Works s BPMN 2.0.

For other, more complex business logic implementations, both products help developers use business rules and apply BPM processes. Red Hat JBoss Fuse Service Works provides this functionality via the Bean, BPM, and Rules components. For BPM components, Red Hat JBoss Fuse Service Works allows access to the latest jBPM 6.0 version, which s BPMN 2.0 business processes. Mule ESB Enterprise s jBPM 4.4,18 with process designs based on jPDL. Mule ESB Enterprise does not BPMN 2.0.

16 Enterprise Integration Patterns table of contents web page — http://www.enterpriseintegrationpatterns.com/toc.html 17 Remote-procedure invocation, publish-subscribe channel, dead letter channel, guaranteed delivery, command message, document message, event message, request-reply, return address, correlation identifier, dynamic router, composed message processor, scatter-gather, routing slip, content filter, claim check, normalizer, messaging gateway, messaging mapper, transactional client, polling consumer, event-drive consumer, competing consumers, message dispatcher, selective consumer, durable subscriber, service activator, detour, message store 18 Drools module documentation — Enterprise http://www.mulesoft.org/documentation/display/current/Drools+Module+Reference

redhat.com

COMPETITIVE REVIEW  Red Hat JBoss Fuse Service Works 6 compared with Mule ESB Enterprise 3.4

5

For business rules and complex event processing, Red Hat JBoss Fuse Service Works allows access to the latest Drools 6.0 version. Mule ESB Enterprise s Drools version 5.0.19 When developing solutions that use business rules or BPM processes, Red Hat JBoss Fuse Service Works developers use SCA components within an SCA composite. The SCA standard allows these and other SCA components to seamlessly interoperate. Mule ESB Enterprise developers must use special components to access each type of functionality. For example, there is a specific BPM module for interacting with jBPM 4.4. There is yet another module for interacting with Drools 5.0. Both products allow business logic to be implemented using Java. With Red Hat JBoss Fuse Service Works, Java business logic is accessed via an SCA component — just like business rules and BPM. The Bean Component is a pluggable container in Red Hat JBoss Fuse Service Works that allows Java classes — or beans — to provide and consume services. This means that you can implement a service by simply annotating a Java class. It also means you can consume a service by injecting a reference to that service directly into your Java class. Mule s implementing Java logic using a plain old Java object (POJO), Spring bean, or Java bean. All Java functionality is accessed via the Java component, which is a message processor building block. 20 If you intend to exchange messages with the Java business logic, then you need to configure transformers in the Mule flow to get data in and out of the Java module. For example, you can use the XML-to-Object module that converts XML to Java bean graph using XStream. Mule ESB Enterprise embeds XStream into the runtime but does not all functionality. For example, XStream annotations are not ed and a feature request is outstanding on this issue. 21 Additionally, the use of XStream for conversions to and from Java objects means Mule developers must become familiar with the XStream project. 22 For example, Mule developers must understand what XStream aliases and converters are in order to use then in the advanced tab of the Object-toXML module dia Mule Studio when used in a flow.

19 Drools module documentation — Enterprise http://www.mulesoft.org/documentation/display/current/Drools+Module+Reference 20 Mule ESB Enterprise java component documentation — http://www.mulesoft.org/documentation/display/current/Java+Component+Reference 21 MuleSoft JIRA issue — https://www.mulesoft.org/jira/browse/MULE-6364 22 XStream project home page — http://xstream.codehaus.org/index.html

redhat.com

COMPETITIVE REVIEW  Red Hat JBoss Fuse Service Works 6 compared with Mule ESB Enterprise 3.4

6

COMPARATIVE DIFFERENCES The following subsections highlight competitive differences between Red Hat JBoss Fuse Service Works and Mule ESB Enterprise. The content provided is not an exhaustive list of all differences. However, it does represent significant points that Red Hat commonly discusses with customers.

OPEN SOURCE LICENSING Get comprehensive Red Hat JBoss Fuse Service Works functionality from a single subscription.

Red Hat JBoss Fuse and MuleSoft Mule ESB Enterprise have open source licensing associated with subscriptions. Red Hat’s middleware platforms are licensed under the of the GNU General Public License and GNU Lesser General Public License with the acquired FuseSource products covered under the Apache Software License (ASL). Each of these licenses can be found in use by other open source projects outside of the Red Hat portfolio. Mule ESB Enterprise licensing varies, depending on if you are using the community or enterprise edition. Mule ESB Community is licensed under the Common Public Attribution License (AL) while Mule ESB Enterprise is licensed using a proprietary MuleSoft license. 23

MORE CONSISTENT COMMUNITY TO ENTERPRISE TRANSITION Both Red Hat and MuleSoft offer community versions of their integration bus software offerings. These open source versions form the basis for later enterprise versions. Enterprise versions (available by subscription) include code changes for bug fixes, security, and other additions that harden the software. From a technical functionality perspective, Red Hat JBoss Fuse Service Works functionality is very close to the JBoss Community projects that contribute to the product packaging. With the exception of JBoss Operations Network, all Red Hat JBoss Fuse Service Works functionality is found in the various community projects. This helps simplify the transition to JBoss Fuse Service Works for customers using the community projects. Transitioning from community projects to JBoss Fuse Service Works has other benefits such as bug and security fixes, platform certification, and more, as presented in “JBoss Enterprise Middleware: Top 10 reasons to subscribe.” 24 MuleSoft, by comparison, has a significant amount of functionality available in its enterprise edition that is not available in its community edition. 25 For example, all security, performance management, and operational control functionality available in the Mule ESB Enterprise is missing from the community edition. Reliability and performance features like high availability and caching are also available only in Mule ESB Enterprise. Such disparity in functionality can arguably point to a completely different solution architect and developer experience when comparing Mule ESB community usage to the enterprise edition.

23 MuleSoft Products and Licensing — http://www.MuleSoft.org/MuleSoft-products-and-licensing 24 JBoss Enterprise Middleware: Top 10 reasons to subscribe — http://www.redhat.com/resourcelibrary/whitepapers/jboss-top-10-reasons-to-subscribe-whitepaper 25 Mule ESB Enterprise web page — http://www.mulesoft.com/mule-esb-enterprise

redhat.com

COMPETITIVE REVIEW  Red Hat JBoss Fuse Service Works 6 compared with Mule ESB Enterprise 3.4

7

DEVELOPER ACCESS TO ADDITIONAL MIDDLEWARE Developers appreciate getting access to all Red Hat JBoss Middleware products for development as part of a Red Hat JBoss Fuse Service Works subscription.

With your Red Hat JBoss Fuse Service Works subscription, you get development rights to all Red Hat JBoss Middleware platforms. Specifically, for every 16 cores of a Red Hat JBoss Middleware subscription, 25 developers gain rights as developers for all Red Hat JBoss Middleware platforms. As a result, developers can easily explore how Red Hat middleware platforms such as Red Hat Data Virtualization, Red Hat JBoss Data Grid, and others complement Red Hat JBoss Fuse Service Works. Unlike a Red Hat middleware subscription, a Mule ESB Enterprise license does not entitle developers access to other MuleSoft products. In addition, MuleSoft does not offer a broad middleware portfolio and is missing a Java EE application platform, business rules management system (BRMS), business process management (BPM), general-use in-memory data grid, and other technology that is found in the Red Hat JBoss Middleware portfolio.

RED HAT PRICE ADVANTAGE Red Hat JBoss Fuse Service Works holds a price advantage over Mule ESB Enterprise. A Red Hat subscription for 16 cores of Red Hat JBoss Fuse Service Works, which includes with management, has an annual list price of $43,500 USD. Mule ESB Enterprise is available from MuleSoft with a paid subscription. According to Gartner 26 and PCWorld 27, the annual list price for the Mule Enterprise suite of products is approximately $6,000 USD per core with silver-level 28 . MuleSoft does not make its pricing information public, so these third-party sources were used. Therefore, as shown in Table A, a 16-core annual subscription for the Mule ESB Enterprise costs approximately $96,000 annually — or more than double a Red Hat JBoss Fuse Service Works annual subscription for the same number of cores. 29

26 Gartner report G00233004, ‘Magic Quadrant for Application Infrastructure for Systematic application integration projects”, June 20, 2012 — http://www.gartner.com/id=2056219 27 “Mule Update Is Data Friendly”, Jun 26, 2012 — http://www.pcworld.com/article/258317/mule_update_is_data_friendly.html 28 MuleSoft subscription tiers — https://www.mulesoft.com/mule-esb- 29 MuleSoft calculation is 2.2 times more and rounded down to 2

redhat.com

COMPETITIVE REVIEW  Red Hat JBoss Fuse Service Works 6 compared with Mule ESB Enterprise 3.4

8

TABLE A: 2-YEAR MULESOFT CALCULATIONS USING 16 CORES

Annual Mule ESB Enterprise subscription with silver level

CORES

ANNUAL SUBSCRIPTION PER CORE

TOTAL

16

$6,000

$96,000

Annual total

$96,000

2-year total MuleSoft cost

$192,000

Note that MuleSoft prices are estimates based on third-party sources

2-YEAR RED HAT JBOSS FUSE SERVICE WORKS SUBSCRIPTION COSTS RED HAT JBOSS FUSE SERVICE WORKS WITH MANAGEMENT, 16 CORE

RED HAT JBOSS FUSE SERVICE WORKS WITH MANAGEMENT, 64 CORE

Annual subscription

$43,500

$162,000

2-years of annual subscription

$87,000

$324,000

Savings versus MuleSoft (USD)

$105,000

$444,000

Further, with a Red Hat subscription (as priced), you get more service incidents and hours of coverage than with a MuleSoft silver subscription. For example, MuleSoft silver-level limits the number of incidents based on the number of cores you subscribe to. With a Red Hat subscription, you get unlimited cases and 24x7 coverage for Red Hat severity 1 and 2 cases. A MuleSoft silver subscription level provides you with only 8x5 .

redhat.com

COMPETITIVE REVIEW  Red Hat JBoss Fuse Service Works 6 compared with Mule ESB Enterprise 3.4

9

GET MORE FOR YOUR DOLLAR A Red Hat JBoss Fuse Service Works subscription includes features that exceed those offered by MuleSoft silver and gold level .

With Red Hat JBoss Middleware, your relationship extends to all stages of the technology life cycle. We encourage you to us — but not just when there’s a problem. The relationship between Red Hat and its customers is truly collaborative and consultative. Typical technicians have 8-10 years of technical experience and can understand and patch code. In addition, Red Hat employees who have contributed to the development of the various middleware components — both on the enterprise team and in the community — are on call to answer questions in depth. 30 You can Red Hat and count on our expertise during all phases of planning, testing, deploying, maintaining, and upgrading your infrastructure. Red Hat s installation, usage, configuration, diagnosis, bug reports, and bug fixes. With a Red Hat subscription, you can gain access to product versions and updates, security updates, unlimited incidents, 24x7 telephone , documentation, hardware and software certifications, and other items detailed on the Red Hat Global Services section of the website. 31 MuleSoft, by comparison, offers three subscription tiers. 32 MuleSoft’s silver and gold levels provide only 8x5 , with a limited number of instances. services in these silver and gold tiers — outside of phone  — are limited to access to community forums, knowledgebase, service packs, and hot patches. 33

FINANCIAL STRENGTH Both Red Hat JBoss Fuse and Mule ESB Enterprise are open source enterprise service buses that have been used in deployment for several years. Mule ESB Enterprise is offered by MuleSoft, a privately held company financed by venture capital since July 2006. 34 MuleSoft does not disclose revenue but InsideView estimates it at $40M USD annually, generated by 180 employees. 35 In comparison, Red Hat is a publicly traded company 36 with over 5,600 worldwide employees, a fiscal 2013 revenue of $1.33 billion, 37 and a reputation as the world’s leading open source and Linux provider. 38

30 “Why subscribe to enterprise open source software? Top ten reasons to use JBoss Enterprise Middleware” — http://www.redhat.com/f/pdf/jb-value-of-sub.pdf 31 Red Hat global services — https://access.redhat.com// 32 MuleSoft ESB page — http://www.mulesoft.com/mule-esb-subscription 33 Mule ESB Enterprise web page — http://www.mulesoft.com/mule-esb-enterprise. Also see MuleSoft ESB page — http://www.mulesoft.com/mule-esb-subscription 34 MuleSoft, About Company web page — http://www.MuleSoft.com/company 35 February 2013, InsideView MuleSoft web page — http://www.insideview.com/directory/MuleSoft-inc 36 Red Hat Investor Relations web page — http://investors.redhat.com/ 37 Red Hat Annual Report 2013 — http://files.shareholder.com/s/RHAT/2893426343x0x657207/97DF4F83606D-4AC5-9153-0B7B49C558CC/SEC-RHAT-1193125-13-173724.pdf 38 Past financial performance is no guarantee of future results

redhat.com

COMPETITIVE REVIEW  Red Hat JBoss Fuse Service Works 6 compared with Mule ESB Enterprise 3.4

10

COMPETITIVE REVIEW  Red Hat JBoss Fuse Service Works 6 compared with Mule ESB Enterprise 3.4

CONCLUSION This high-level comparison between Red Hat JBoss Fuse Service Works 6.0 and Mule ESB Enterprise 3.4 has found some functional similarities and many technical differences between the products. Only Red Hat JBoss Fuse focuses on using open standards for both product implementation and integration communication. For example, SCA is used as the service assembly framework for building solutions. BPMN is used for business process management, and Camel for service routing. Plus, only Red Hat JBoss Fuse Service Works allows you to work with enterprise versions of current jBPM and Drools technologies sourced from JBoss community projects. Aside from technical differentiators, there are also differences in overall company stature that go beyond employee counts and revenues. Red Hat offers a much broader scope of products, including middleware, Linux, storage, and cloud offerings. To implementation and use of these products, Red Hat also has built a staff of experienced people ready to work with customers. Our associates in professional services can be contracted to participate in customer engagements. Red Hat JBoss Fuse Service Works, like other Red Hat JBoss Middleware products, is available in 16- and 64-core entitlements, as a subscription that is renewed annually or (for a discount) every 3 years. With Red Hat JBoss Fuse Service Works, you get unlimited incident , version updates, and bug fixes, plus access to the Red Hat Customer Portal, for the full life cycle of your subscription. The economic difference between Red Hat JBoss Fuse Service Works and Mule ESB Enterprise is significant. A 2-year, 16-core Red Hat JBoss Fuse Service Works managed subscription is more than $100K less than Mule ESB Enterprise at list price—or 45.3% of the MuleSoft cost. The savings you realize by choosing Red Hat can let you to start more projects, deploy technology more pervasively within your enterprise, and apply more of your time and budget towards innovation. Innovate more and spend less with a Red Hat JBoss Fuse Service Works subscription. your Red Hat sales professional for more information.

ABOUT RED HAT Red Hat is the world’s leading provider of open source solutions, using a community-powered approach to provide reliable and high-performing cloud, virtualization, storage, Linux, and middleware technologies. Red Hat also offers award-winning , training, and consulting services. Red Hat is an S&P company with more than 70 offices spanning the globe, empowering its customers’ businesses.

facebook.com/redhatinc @redhatnews linkedin.com/company/red-hat

redhat.com #11851667_v3_0314

NORTH AMERICA 1 888 REDHAT1

EUROPE, MIDDLE EAST, AND AFRICA 00800 7334 2835 [email protected]

ASIA PACIFIC +65 6490 4200 [email protected]

LATIN AMERICA +54 11 4329 7300 [email protected]

Copyright © 2014 Red Hat, Inc., Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks of Red Hat, Inc., ed in the U.S. and other countries. Linux® is the ed trademark of Linus Torvalds in the U.S. and other countries.