Talend update
I chatted yesterday at TDWI with Yves de Montcheuil of Talend, as a follow-up to some chats at Teradata Partners in October. This time around I got more metrics, including:
- Talend revenue grew 6-fold in 2008.
- Talend revenue is expected to grow 3-fold in 2009.
- Talend had >400 paying customers at the end of 2008.
- Talend estimates it has >200,000 active users. This is based on who gets automated updates, looks at documentation, etc.
- ~1/3 of Talend’s revenue is from large customers. 2/3 is from the mid-market.
- Talend has had ~700,000 downloads of its core product, and >3.3 million downloads in all (including documentation, upgrades, etc.)
It seems that Talend’s revenue was somewhat shy of $10 million in 2008.
Specific large paying customers Yves mentioned include:
- Virgin Mobile – for a full EDW, apparently
- US Cellular – collecting technical information from, you guessed it, cell towers
- Verizon (the part of Verizon that is using Vertica)
- eBay
- Yahoo
Yves also told a cool story in operational rather than analytic data integration, but I’ll save that for another time.
Yves and I also got a little more concrete than last time discussing what the community contributes to Talend. Specifics included:
- Of Talend’s ~400 different connectors, ~1/3 come from the community.
- Community members support each other, and paying customers as well, in the forums.
- Talend has ~1000 beta testers.
- Community members seem to be doing a lot of language translation. For the 12,000 text strings in the Talend Open Studio user interface, translation is at least half done in at least Chinese, German, Spanish, and Portuguese.
I once again forgot to ask Yves the difference between the community and paid product editions, but a visit to the Talend show booth later on cleared that up quickly. The three biggies seems to be:
- Administrative console
- Activity monitoring console (I gather that’s the run-time administrative piece, more or less)
- Shared (as opposed to single-user) repository
Yves also offered the results of a user survey (free and paid alike). Supposedly, the reasons for selecting Talend, in declining order, are:
- Performance
- Features
- Vendor independence (presumably vs. database management vendors)
- Price
- Access to source code
Frankly, while I don’t doubt Yves’ sincerity in sharing those results, I take them with a grain of salt. Survey design is notoriously tricky.
Comments
5 Responses to “Talend update”
Leave a Reply
Talend is written in java and generates a java or perl code. How the performance be its top reason. I could understand the lower cost but definitely not the performance
What Talend is written in could only affect developer-UI or generation-time performance, not run-time.
I don’t recall what languages Talend generates, specifically how compiled any of them are.
CAM
[…] Podcast zum anhören. Ausserdem hatte Yves ein Gespräch mit jemandem von Monash Research. Die Zusammenfassung des Gesprächs enthält allerdings nicht viel Neues. Aber ich möchte das hier trotzdem nicht unerwähnt […]
If you don’t understand how performance can be the top reason you either dont understand the efficent nature of perl execution. perl is like poo off a JCB shovel. perl should be called pETaL
[…] so I’m talking with vendors again, including Informatica — but not Talend, which seems reluctant to let me talk with somebody technical, and also not the secrecy-obsessed Ab […]