Download to read offline
Uploaded byKETL Limited
Talend community user group Bristol: commercial versus community version
The document outlines the agenda for the Talend Community User Group meeting held in October 2015, focusing on the differences between community and commercial versions of Talend products. It highlights achievements, performance metrics, and support issues regarding community solutions. The conclusion questions the practicality of accomplishing everything with community tools compared to commercial offerings.
Talend community user group Bristol: commercial versus community version
- 1. www.ketl.co.uk Talend community user group O1October 2015
- 2. Agenda 1. Intro withIan Cray 2. Community vs. Commercial 3. Talend MDM, ESB and v6
- 3. Community vs. Commercial Whatcan be achieved with Community? Is it really free? Comparisons • Technical • Productivity • Performance • Support
- 4. Talend - ProductSolution v
- 5. Talend and OpenSource 2m downloads of Community products 100k members of TalendForge • Forum • Code samples • Custom Components Sponsors of the Apache Software Foundation Member of the Eclipse Foundation
- 6. Technical Differences Some extracomponents (esp. DQ) CDC tParallelize Dynamic Schema
- 7. Productivity Differences Shared Metadata/ Development Joblets Job Compare TAC AMC Reference Projects
- 8. Performance Differences High Availability LoadBalancing Failover Execution Plans Error Recovery
- 9. Support Support not includedin Community version Indemnity Warranty
- 10. Community vs. Commercial- Summary Is it possible to do everything in Community that can be done in Commercial? • Yes (technically) Is it practical to do everything in Community that can be done in Commercial? • No
- 11. www.ketl.co.uk 13-14 Orchard Street,Bristol BS1 5EH +44 (0)117 905 5323 info@ketl.co.uk @KETL_BI Thanks for listening Next event 28th January so let Helen know your ideas for Talend topics to cover and volunteers to present > Ian Cray call: 07813 899 046 email: Ian@ketl.co.uk
Editor's Notes
- #3 3rd TCUG New Venue New topics needed – suggestions
- #5 Purpose of the slide: Describe the solutions we can propose, explore what could interest the prospect and describe the benefits our customers can get from our unified platform. Key themes: Talend progressively built best of breed solutions for all integration needs: 2007: Talend data integration was quickly adopted by developers to increase their productivity by giving them a design environment for data flows and transformations instead of developing hand-coded scripts. Through the Unified Platform in 2007, users could collaborate, monitor, schedule and administer their data integration jobs resulting in even greater productivity gains. The unified platform was only available through payment of a commercial subscription. The flow was simple – seed to DI developers and flow upwards to the unified platform. 2008: introduction of data quality. Second seeding flow related to data integration was to provide to data analysts a free way to profile and understand the quality of their data in terms of duplicates, non-conformity to a given pattern, blank fields, etc. the commercial offering of DQ provides the capability to correct these data errors and enrich/augment data through mainly data integration technologies. It also provides the capabilities to monitor, schedule and administer all of the data quality jobs that would correct the data. Seeding flowed from profiling of data, across to correcting data and up to unified platform to administer both DQ and DI centrally. 2009 Introduction of MDM. MDM is a central hub that stores and manages reference data used by multiple applications and data sources. It leverages both data quality (matching) and integration technologies (synchronizing reference data in the hub with other data sources and applications). The open source version allowed users to develop POCs while the commercial version provides additional features such as workflow capabilities (to govern who has the right to change reference data) as well as the Unified Platform which enables users to administer all of the DI, and DQ jobs associated with their MDM deployments as well as all other DI / DQ jobs deployed across an organization. This opened a third seeding flow upwards to the Unified Platform and across DI and DQ. 2010: Introduction of Application Integration. AI, manifested primarily by an ESB, enables users to connect/integrate applications amongst themselves in real time through web services. Instead of having point-to-point integration flows between applications, users only have to design a single point to hub integration flow. When an application is retired, only one integration point needs to be redone instead of all point-to-point integrations. In addition, transformations (for DQ and DI purposes) can be done in the bus and be provided as a service. Lastly, instead of connecting a MDM hub through point to point DI jobs it can be done through web services. The seeding open source version of the product enables users to develop web services and have the infrastructure to route these services. The fourth evolution of the unified platform enables users to manage centrally all of the DI, DQ jobs and web services centrally and also enhance the collaboration of developers/users through a central metadata repository. We realized before anyone else the integration of DI, DQ, MDM, ESB, and BPM Each solution/product is modular, simple, best-of-breed while working on a common platform Unified Studio: (rich client / Eclipse based) Eclipse is a well known framework, widely used & robust. + Same GUI, same logic, same clipboard drive to flat learning curve & fast development Unified Repository: (CWM compliant) All "artifacts" from all tools are saved in the same Repository it allows faster development reusing existing element (Metadata...) but, much more important from my perspective, it allows to ensure consistency from end to end Unified Administration tools: for deployment, scheduling & monitoring. Lightweight (-> no deployment), GWT based, Flat learning curve also for operation manager… Unified Runtime: same container can handle either batch transformation, message transformation (camel route) & services. Easy to deploy, upgrade & monitor. + allows consistency for network connections (firewall management...) for admin, log...