Open source vs commercial esb and api management platform draft wh1 for smals

Open source vs commercial esb and api management platform draft wh1 for smals

• 1.
  1 | BENEFITS OFOPEN SOURCE © 2015 Software AG. All rights reserved. For internal use only
• 2.
  2 | ©2015 Software AG. All rights reserved. For internal use only “We’re committed to commercial software. Open source is good, but it requires so many more resources to support in the long run.” – Enterprise Architect for a major US grocery chain
• 3.
  3 | BENEFITS OFCOMMERCIAL SOFTWARE (1) © 2015 Software AG. All rights reserved. For internal use only
• 4.
  4 | BENEFITS OFCOMMERCIAL SOFTWARE (2) © 2015 Software AG. All rights reserved. For internal use only
• 5.
  5 | COUNTERING OPENSOURCE CLAIMS © 2015 Software AG. All rights reserved. For internal use only Countering OSS Claims OSS Claim Counter-Response OSS avoids vendor lock-in • More true for massive projects such as Linux, or narrowly-defined components and utilities used as project building-blocks; • Less true for enterprise-class products (middleware, In-memory data stores), unless the end user has substantial in-house resources and commitment; • Who is responsible for the (enhancement) commits? Is it a small group of vendor employees? All required enhancements are generated for free by the OSS community • Less true for enterprise-class products, especially if the requirement is complex, unpopular, highly-performance, high scale, etc. – in this case the end-user will do the work themselves or rely on a vendor. Constant scrutiny of the OSS code by the OSS community ensures maximum security • Recent instances have shown source code can lay exposed for long periods without the community spotting security flaws; • Do your in-house developers have hours to spend scanning OSS source code for security flaws?
• 6.
  6 | SUMMARY © 2015Software AG. All rights reserved. For internal use only
• 7.
  7 | ©2015 Software AG. All rights reserved. For internal use only Questions?