Mule Community edition vs Enterprise edition - Feature Comparison?

Question

It should be a simple google ... but I drew a space. I guess he should be out there somewhere, can someone help me find him?

I need a simple comparison that tells me what is located and what goes beyond the community, and the corporate version?

* For example, DataMapper is not included in the Community, but it is not clear until you try to deploy, I really would like to save a lot of effort in vain.

Thanks.

Answer 1

MuleSoft provides a list of comparisons and features here: http://www.mulesoft.com/platform/soa/mule-esb-enterprise

This information indicates that Datamapper is an enterprise only. It has a common expression around corporate connectors, but you can see which ones are a corporation or community through mulesoft.org/connectors?class=premium

Some vehicles (mainly JDBC) have business equivalents that are documented on separate pages of the transportation documentation: http://www.mulesoft.org/documentation/display/current/JDBC+Transport+Reference

Answer 2

The slope of the old thread, but this page contains a simple list with simple supported / not supported, as well as areas of impact of such a function, not included in CE.

http://www.whishworks.com/blog/mule-esb-community-vs-enterprise-edition/

However, adding the same content here so that if the connection becomes dead, the content is not lost. Just click the "Delete Code Code"> "Full Page" button to see the full table.

<p><strong>High Availability and Performance</strong> </p> <table class="matrix" style="height: 247px;" width="650"> <tbody> <tr> <td width="173"><b>Feature</b> </td> <td width="173"><b>Community</b><b> Edition</b> </td> <td width="173"><b>Enterprise Edition (G) / (S)</b> </td> <td width="173"><b>Enterprise Edition (P)</b> </td> <td width="173"><b>Impact</b> </td> </tr> <tr> <td width="173">High Availability</td> <td width="173">No Support</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Message Loss and Transaction failure</td> </tr> <tr> <td width="173">Resilience</td> <td width="173">No Support</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Impact on effort to take care of state full&nbsp; and failure scenarios</td> </tr> <tr> <td width="173">Caching</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Performance Impact</td> </tr> </tbody> </table> <p>&nbsp;</p> <p><strong>Development</strong> </p> <table class="matrix" width="650"> <tbody> <tr> <td width="173"><b>Feature</b> </td> <td width="173"><b>Community</b><b> Edition</b> </td> <td width="173"><b>Enterprise Edition (G) / (S)</b> </td> <td width="173"><b>Enterprise Edition (P)</b> </td> <td width="173"><b>Impact</b> </td> </tr> <tr> <td width="173">Anypoint Templates</td> <td width="173">No Support</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Saves development and design effort by using templates. Guesstimated to be 40 to 60% time saving depending on how close the use case matches to the template.</td> </tr> <tr> <td width="173">Transaction Management</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Data loss and Impact on development effort</td> </tr> <tr> <td width="173">Batch Manager</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Impact on Development &amp; Support Effort</td> </tr> <tr> <td width="173">Batch Process component</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Impact on Development &amp; Support Effort</td> </tr> <tr> <td width="173">JDBC Enterprise Connector</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">for handling Batch statements, used in Data Integration project. Performance hit.</td> </tr> <tr> <td width="173">Anypoint Datamapper</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Impact on Development</td> </tr> </tbody> </table> <p>&nbsp;</p> <p><strong>Operational Support</strong> </p> <table class="matrix" width="650"> <tbody> <tr> <td width="173"><b>Feature</b> </td> <td width="173"><b>Community</b><b> Edition</b> </td> <td width="173"><b>Enterprise Edition (G) / (S)</b> </td> <td width="173"><b>Enterprise Edition (P)</b> </td> <td width="173"><b>Impact</b> </td> </tr> <tr> <td width="173">Mule Management Console</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Impact on Support</td> </tr> <tr> <td width="173">SLA and email Alerts</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Impact on Support and Availability</td> </tr> <tr> <td width="173">SNMP Monitoring</td> <td width="173">No</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Impact on Support and Availability</td> </tr> <tr> <td width="173">HTTP Polling</td> <td width="173">No</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Impact on Support and Availability. Mule provides Http polling of service for availability.</td> </tr> <tr> <td width="173">Deployment Management</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Impact on Support</td> </tr> </tbody> </table> <p>&nbsp;</p> <p><strong>Security</strong> </p> <table class="matrix" width="650"> <tbody> <tr> <td width="173"><b>Feature</b> </td> <td width="173"><b>Community</b><b> Edition</b> </td> <td width="173"><b>Enterprise Edition (G) / (S)</b> </td> <td width="173"><b>Enterprise Edition (P)</b> </td> <td width="173"><b>Impact</b> </td> </tr> <tr> <td width="173">Role based security</td> <td width="173">Not Supported</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Major effort to custom develop</td> </tr> <tr> <td width="173">Oauth 2.0 – Secure Token Provider</td> <td width="173">Not Supported</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Major effort to custom develop</td> </tr> <tr> <td width="173">Message Encryption</td> <td width="173">Not Supported</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Major effort to custom develop</td> </tr> <tr> <td width="173">SAML 2.0 Module</td> <td width="173">Not Supported</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Major effort to custom develop</td> </tr> <tr> <td width="173">Secure Property Holder</td> <td width="173">Not Supported</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Keeps password and other confidential text in encrypted format. This cannot be custom built as it links directly to your endpoint.</td> </tr> <tr> <td width="173">IP Based Filtering</td> <td width="173">Not Supported</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">IP based filter is available in EE version for filtering endpoints based on inbound IP and requests can be filtered using LDAP.</td> </tr> </tbody> </table> <p>&nbsp;</p> <p><strong>Support</strong> </p> <table class="matrix" width="650"> <tbody> <tr> <td width="173"><b>Feature</b> </td> <td width="173"><b>Community</b><b> Edition</b> </td> <td width="173"><b>Enterprise Edition (G) / (S)</b> </td> <td width="173"><b>Enterprise Edition (P)</b> </td> <td width="173"><b>Impact</b> </td> </tr> <tr> <td width="173">License</td> <td width="173">Free</td> <td width="173">Purchase Minimum 2 Cores</td> <td width="173">Purchase Minimum 4 (2+2) for HA</td> <td width="173">Licence Cost</td> </tr> <tr> <td width="173">Hardened Code</td> <td width="173">No Support</td> <td width="173">Yes</td> <td width="173">Yes</td> <td width="173">Impact on stability and performance</td> </tr> <tr> <td width="173">SLA</td> <td width="173">Forums</td> <td width="173">8/5, 24 Hours Response Time</td> <td width="173">24/7, 2 Hours Response Time</td> <td width="173">Impact on support</td> </tr> <tr> <td width="173">Hot patches &amp; Service packs</td> <td width="173">No Support</td> <td width="173">Supported</td> <td width="173">Supported</td> <td width="173">Impact on support and availability</td> </tr> </tbody> </table> 

-Shanky G.