I can't imagine getting my boss to pay for something like TIBCO. That would
require quite a sales job.
With one exception, the developers I know wouldn't even use Camel. They
tend to reinvent the wheel. But they do use Spring and a few even use
Spring Integration.
In order to commit to something
Exactly. And what many fail to see is that closed source is – in many cases
– leveraging OSS under the hood. Sometimes the vendor will be nice and make
it evident (e.g. IBM WebSphere being quite transparent in their docs about
using Apache Aries, they also contribute, etc.).
But in other cases,
Hi Raul
Did you get a chance to continue working on this?
I think for #3 its due to the openes of the source code that people
dive in and help fix those vulnerabilities as well. And as you say we
are very open and they get proper registerede with a CVE and listed in
the public. And we do put out
Just found this marketing landing page published on social networks. It's
made by TIBCO and attempts to highlight the downsides of Open Source ESBs.
You don't need to be a rocket scientist to gather what exact ESB they are
targeting (not us): just look at the images.
Hi Raul
Well spotted.
Well I guess its only a sign that Camel / Open Source / SMX / Karaf /
Others Camel like ESBs make a dent into the old world.
Now its Tibco to take notice.
Their 4 myths seems very generic to me, as its not really about ESB
but Open Source in general.
IBM have done their
