Sybase builds on Coral8 source
So this is interesting. If I understand this correctly, Sybase now has the same engine as the merged Aleri+Coral8. Or at least one of the Aleri’s engines, I think they have two engines which they have plans to support.
It will be interesting how Aleri handles competetion from Sybase as they could now, at least theorethically, build the same kind of solutions.
So first Coral8 sells it’s source code to Sybase and then Aleri buys Coral8. Interesting times…
"Sybase is entering the Complex Event Processing business with the introduction of Sybase CEP, which is being offered – initially at least – as an option to its RAP – The Trading Edition capital markets analytics platform. The product results from the vendor’s licensing of the source code for Coral8’s CEP engine," – from here
Ouch, that’s got to hurt former Coral8ers.
Hi Marco,
This depiction is not completely accurate. The Sybase license for Coral8 CEP is ONLY for bundled offerings such as Sybase RAP. Sybase CANNOT sell a standalone CEP product based on their Coral8 license.
All the best,
John-
Thanks for the clarification John. I think the article actually hints of the opposite – “initialy at least” – and made me think this was their first step towards a generic CEP offering. It makes sense to OEM a CEP building block into RAP instead of building it itself.
Hello John,
Are there other details on the deal? Is this a one time source code tree fork? Will Sybase get new versions from Aleri? It would be interesting to hear if Sybase they will develop it itself further or if bugfixes, patches and new features will come from Aleri’s developers?
Hi Era,
Sorry, we are not releasing more details on the terms of the deal. Those are business terms between Sybase and Aleri. For a our complete description on the deal and our OEM strategy, please feel free to visit our blog:
http://www.coral8.com/blogs/coral8-blog
Thanks,
John-
>>>> Sorry, we are not releasing more details on the terms of the deal. Those are business terms between Sybase and Aleri. <<<<
Sorry John, but this non-statement will cause more confusion, causing more people to speculate on their own.
Era, Johan, Marc,
This would indeed be interesting to know for any Sybase RAP customers. A fork of the source code leaves Sybase in a situation where it must maintain an extremely complex product if the updates are not coming in from Aleri. If I would be a customer, I certainly would be interested in this in the long term. But I understand John if they don’t want to talk about the details of that deal in public.
/Marco
You have to wonder why Coral8 accepted to license its source rather than just its binaries and a few API and docs for ISVs as any other “classic” OEM deal would much likely imply.
Now with the Coral8 takeover by Aleri, you also have to wonder how this source license will be maintained while Aleri and Coral8 are merging their sources.
Despite John ‘ description in Coral8 blog on the virtues for vendors of such OEM / resell / upsell agreements, licensing the product source is somewhat an unusual mean to this end.
Maybe Sybase just wanted something that they could continue developing their own CEP engine upon, instead of starting from scratch. Even if the do a complete fork as speculated it would give them a good start to build upon the Coral8 source base. Did not Microsoft once buy some Sybase source which now is SQL server? Maybe Sybase learned that this is a good way to put a product on the market and buy some time while you learn how to build upon the code base yourself…