DOCSLIB.ORG

Challenges and Experiences in Building an Efficient Apache Beam

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Challenges and Experiences in Building an Efficient Apache Beam Challenges and Experiences in Building an Efficient Apache Beam Runner For IBM Streams Shen Li† Paul Gerver* John MacMillan* Daniel Debrunner* William Marshall* Kun-Lung Wu† {shenli, pgerver}@us.ibm.com, [email protected], {debrunne, wcmarsha, klwu}@us.ibm.com †IBM Research AI *IBM Watson Cloud Platform ABSTRACT 1. INTRODUCTION This paper describes the challenges and experiences in the Distributed stream computing has been adopted by a rap- development of IBM Streams runner for Apache Beam. Apa- idly increasing number of industrial applications. For exam- che Beam is emerging as a common stream programming in- ple, social networks use streaming analytic systems to de- terface for multiple computing engines. Each participating tect trending topics and react to news events. Peer-to-peer engine implements a runner to translate Beam applications ridesharing and food delivery companies process streaming into engine-specific programs. Hence, applications written spatial-temporal data to timely pair supply and demand. with the Beam SDK can be executed on different under- Online advertisement platforms continuously optimize con- lying stream computing engines, with negligible migration tent placement to maximize monetary gains. Digital health- penalty. IBM Streams is a widely-used enterprise streaming care providers collect and evaluate wearable device sensory platform. It has a rich set of connectors and toolkits for easy data to offer lifestyle suggestions and launch critical alarms. integration of streaming applications with other enterprise Data centers monitor hardware and software status around applications. It also supports a broad range of programming the clock to capture performance anomalies. Numerous ap- language interfaces, including Java, C++, Python, Stream plications seek the ability to quickly react to dynamic stream- Processing Language (SPL) and Apache Beam. This pa- ing data, as it is either a mandatory requirement or a com- per focuses on our solutions to efficiently support the Beam petitive advantage. programming abstractions in IBM Streams runner. Beam These demands catalyze the developments of various types organizes data into discrete event time windows. This de- of stream computing engines, including Apex [2], AthenaX sign, on the one hand, supports out-of-order data arrivals, [10], Google Dataflow [20, 11], Flink [5, 22], Gearpump [6], but on the other hand, forces runners to maintain more Heron [18, 24], Samza [8, 31], Spark Streaming [37, 38], IBM states, which leads to higher space and computation over- Streams [12, 35, 28, 34, 33, 32, 26], etc. However, from the head. IBM Streams runner mitigates this problem by ef- perspective of application developers, the decision is not al- ficiently indexing inter-dependent states, garbage-collecting ways straightforward when exposed to abundant underlying stale keys, and enforcing bundle sizes. We also share per- engine options. Each stream computing engine designs their formance concerns in Beam that could potentially impact own programming API which means they are not compati- applications. Evaluations show that IBM Streams runner ble with each other. outperforms Flink runner and Spark runner in most scenar- Recently, the emerging Apache Beam [3] project aims to ios when running the Beam NEXMark benchmarks. IBM provide a common programming interface. The Beam SDK Streams runner is available for download from IBM Cloud inherits from Google Cloud Dataflow API [20]. It is a uni- Streaming Analytics service console. fied model for both batch and streaming processing. Ap- plication pipelines written using the Beam API can run on PVLDB Reference Format: different underlying engines without modifying their appli- Shen Li, Paul Gerver, John MacMillan, Daniel Debrunner, William cations, which significantly reduces the switching overhead. Marshall, Kun-Lung Wu. Challenges and Experiences in Building Beam requires each participating engine to provide a run- an Efficient Apache Beam Runner For IBM Streams. PVLDB, 11 (12): 1742-1754, 2018. ner that is responsible for converting Beam applications into DOI: https://doi.org/10.14778/3229863.3229864 their engine native programs and submitting the programs for execution. The Beam SDK focuses on application logic and relies on runners and engines to figure out low-level sys- tem details, such as parallelism, graph fusion, consistency, durability, and failure recovery. This work is licensed under the Creative Commons Attribution- NonCommercial-NoDerivatives 4.0 International License. To view a copy This paper shares our experiences of building IBM Streams of this license, visit http://creativecommons.org/licenses/by-nc-nd/4.0/. For runner for Apache Beam. IBM Streams is a widely-used any use beyond those covered by this license, obtain permission by emailing stream computing platform for high-throughput and low- [email protected]. latency applications. It has a rich set of more than 80 con- Proceedings of the VLDB Endowment, Vol. 11, No. 12 nectors and toolkits, many of them open-sourced [14, 12], Copyright 2018 VLDB Endowment 2150-8097/18/8. allowing a developer to easily integrate their streaming ap- DOI: https://doi.org/10.14778/3229863.3229864 1742 plications with many other enterprise applications and ser- The remainder of the paper is organized as follows. Sec- vices. It supports a broad range of programming language tion 2 briefly illustrates the background for Apache Beam interfaces, including Java, C++, Python, Stream Processing and IBM Streams. Section 3 elaborates upon optimizations Language (SPL) [27] and so on. As Beam gains increasing in Streams runner. Implementation details are described in attention, supporting the Beam SDK further broadens the Section 4. Section 5 shares evaluation results, and further programming interfaces of IBM Streams, allowing stream discussions and suggestions are presented in Section 6. Sec- applications written in Beam to take advantages of the en- tion 7 summarizes related work. Finally, Section 8 concludes terprise strength of IBM Streams and its rich set of connec- the paper. tors and toolkits. Streams runner traverses a Beam pipeline and creates a 2. BACKGROUND directed acyclic graph (DAG) that conveys the same appli- This section briefly introduces the Apache Beam model cation logic using the Java API of the open-source Streams and IBM Streams runner design. Topology toolkit [14]. Then, the DAG can be automatically submitted to the IBM Streams Runtime or an IBM Cloud 2.1 Apache Beam Streaming Analytics service [12]. The Streams runtime has Apache Beam is a unified model for both streaming and already been optimized in the past decade in many aspects batch data processing, which has attracted increasing at- including elasticity [34], windowing efficiency [35], consis- tention from both academia and industry. Applications use tency [28], and load balancing [33]. Hence, IBM Streams the Beam SDK to build a pipeline (DAG) that consists of runner mainly focuses on improving the efficiency of indi- PCollections and PTransforms. A PCollection can be ei- vidual Beam operators. ther a bounded dataset or an unbounded data stream. A The challenges of designing the runner lie in how to handle PTransform takes one or multiple PCollections as inputs, ap- Beam windows and states. One challenge occurs in multi- plies user-defined functions, and produces new PCollections. input multi-output Beam operators whose states from in- The Beam SDK provides a rich set of composite PTransforms put streams are interdependent. Elements from one input based on six types of primitive PTransforms as described be- stream can refer to past or even future states of other input low. streams. When the requested states are not yet available, the operator needs to hold the element and instantly retrieve • Source creates a new PCollection from a data struc- it once the state becomes ready. Efficiently indexing pend- ture or an IO connector. ing states and elements are not trivial when applications use large fan-in operators with excessively long lookahead dis- • Window uses user-defined WindowFn to assign windows tances. To address this problem, Streams runner maintains to elements. a specialized DAG structure, which is called Pending States Graph, to index interdependent windows. Another chal- • ParDo takes one main input PCollection and multiple lenge emerges when serving an evolving set of keys. The side input PCollections. It applies a user-defined DoFn runner has to promptly detect and delete obsolete keys to to every element from the main input PCollection, prevent hitting an out-of-memory error. To track evolving and produces zero or more output PCollections. The contents with minimum overhead, Streams runner dissects DoFn can access windowed states (View) from side input keyed states into smaller components, and organizes them PCollections. into multiple interleaving ordered lists, which helps to delete • View converts every window of a PCollection into a obsolete states with low computational complexity. These data structure (e.g., List, Map, Set, Singleton, etc.) two techniques collectively boost the throughput of our run- using an application-specified function. These data ner by more than 100 fold when running query 4 and 5 from structures are later consumed as side inputs by ParDo Beam’s NEXMark benchmark [15]. PTransforms. Evaluations are conducted using NEXMark, and we de- veloped a microbenchmark to attain a more in-depth and • GroupByKey groups values with the same key in the comprehensive view of different runners. Results show
Load more

Recommended publications
  • Regeldokument
    Master’s degree project Source code quality in connection to self-admitted technical debt Author: Alina Hrynko Supervisor: Morgan Ericsson Semester: VT20 Subject: Computer Science Abstract The importance of software code quality is increasing rapidly. With more code being written every day, its maintenance and support are becoming harder and more expensive. New automatic code review tools are developed to reach quality goals. One of these tools is SonarQube. However, people keep their leading role in the development process. Sometimes they sacrifice quality in order to speed up the development. This is called Technical Debt. In some particular cases, this process can be admitted by the developer. This is called Self-Admitted Technical Debt (SATD). Code quality can also be measured by such static code analysis tools as SonarQube. On this occasion, different issues can be detected. The purpose of this study is to find a connection between code quality issues, found by SonarQube and those marked as SATD. The research questions include: 1) Is there a connection between the size of the project and the SATD percentage? 2) Which types of issues are the most widespread in the code, marked by SATD? 3) Did the introduction of SATD influence the bug fixing time? As a result of research, a certain percentage of SATD was found. It is between 0%–20.83%. No connection between the size of the project and the percentage of SATD was found. There are certain issues that seem to relate to the SATD, such as “Duplicated code”, “Unused method parameters should be removed”, “Cognitive Complexity of methods should not be too high”, etc.
    [Show full text]
  • Trifacta Data Preparation for Amazon Redshift and S3 Must Be Deployed Into an Existing Virtual Private Cloud (VPC)
    Install Guide for Data Preparation for Amazon Redshift and S3 Version: 7.1 Doc Build Date: 05/26/2020 Copyright © Trifacta Inc. 2020 - All Rights Reserved. CONFIDENTIAL These materials (the “Documentation”) are the confidential and proprietary information of Trifacta Inc. and may not be reproduced, modified, or distributed without the prior written permission of Trifacta Inc. EXCEPT AS OTHERWISE PROVIDED IN AN EXPRESS WRITTEN AGREEMENT, TRIFACTA INC. PROVIDES THIS DOCUMENTATION AS-IS AND WITHOUT WARRANTY AND TRIFACTA INC. DISCLAIMS ALL EXPRESS AND IMPLIED WARRANTIES TO THE EXTENT PERMITTED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE AND UNDER NO CIRCUMSTANCES WILL TRIFACTA INC. BE LIABLE FOR ANY AMOUNT GREATER THAN ONE HUNDRED DOLLARS ($100) BASED ON ANY USE OF THE DOCUMENTATION. For third-party license information, please select About Trifacta from the Help menu. 1. Quick Start . 4 1.1 Install from AWS Marketplace . 4 1.2 Upgrade for AWS Marketplace . 7 2. Configure . 8 2.1 Configure for AWS . 8 2.1.1 Configure for EC2 Role-Based Authentication . 14 2.1.2 Enable S3 Access . 16 2.1.2.1 Create Redshift Connections 28 3. Contact Support . 30 4. Legal 31 4.1 Third-Party License Information . 31 Page #3 Quick Start Install from AWS Marketplace Contents: Product Limitations Internet access Install Desktop Requirements Pre-requisites Install Steps - CloudFormation template SSH Access Troubleshooting SELinux Upgrade Documentation Related Topics This guide steps through the requirements and process for installing Trifacta® Data Preparation for Amazon Redshift and S3 through the AWS Marketplace.
    [Show full text]
  • Portable Stateful Big Data Processing in Apache Beam
    Portable stateful big data processing in Apache Beam Kenneth Knowles Apache Beam PMC Software Engineer @ Google https://s.apache.org/ffsf-2017-beam-state [email protected] / @KennKnowles Flink Forward San Francisco 2017 Agenda 1. What is Apache Beam? 2. State 3. Timers 4. Example & Little Demo What is Apache Beam? TL;DR (Flink draws it more like this) 4 DAGs, DAGs, DAGs Apache Beam Apache Flink Apache Cloud Hadoop Apache Apache Dataflow Spark Samza MapReduce Apache Apache Apache (paper) Storm Gearpump Apex (incubating) FlumeJava (paper) Heron MillWheel (paper) Dataflow Model (paper) 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 Apache Flink local, on-prem, The Beam Vision cloud Cloud Dataflow: Java fully managed input.apply( Apache Spark Sum.integersPerKey()) local, on-prem, cloud Sum Per Key Apache Apex Python local, on-prem, cloud input | Sum.PerKey() Apache Gearpump (incubating) ⋮ ⋮ 6 Apache Flink local, on-prem, The Beam Vision cloud Cloud Dataflow: Python fully managed input | KakaIO.read() Apache Spark local, on-prem, cloud KafkaIO Apache Apex ⋮ local, on-prem, cloud Apache Java Gearpump (incubating) class KafkaIO extends UnboundedSource { … } ⋮ 7 The Beam Model PTransform Pipeline PCollection (bounded or unbounded) 8 The Beam Model What are you computing? (read, map, reduce) Where in event time? (event time windowing) When in processing time are results produced? (triggers) How do refinements relate? (accumulation mode) 9 What are you computing? Read ParDo Grouping Composite Parallel connectors to Per element Group
    [Show full text]
  • The Forrester Wave™: Streaming Analytics, Q3 2019 the 11 Providers That Matter Most and How They Stack up by Mike Gualtieri September 23, 2019
    LICENSED FOR INDIVIDUAL USE ONLY The Forrester Wave™: Streaming Analytics, Q3 2019 The 11 Providers That Matter Most And How They Stack Up by Mike Gualtieri September 23, 2019 Why Read This Report Key Takeaways In our 26-criterion evaluation of streaming Software AG, IBM, Microsoft, Google, And analytics providers, we identified the 11 most TIBCO Software Lead The Pack significant ones — Alibaba, Amazon Web Forrester’s research uncovered a market in which Services, Cloudera, EsperTech, Google, IBM, Software AG, IBM, Microsoft, Google, and TIBCO Impetus, Microsoft, SAS, Software AG, and Software are Leaders; Cloudera, SAS, Amazon TIBCO Software — and researched, analyzed, Web Services, and Impetus are Strong Performers; and scored them. This report shows how each and EsperTech and Alibaba are Contenders. provider measures up and helps application Analytics Prowess, Scalability, And development and delivery (AD&D) professionals Deployment Freedom Are Key Differentiators select the right one for their needs. Depth and breadth of analytics types on streaming data are critical. But that is all for naught if streaming analytics vendors cannot also scale to handle potentially huge volumes of streaming data. Also, it’s critical that streaming analytics can be deployed where it is most needed, such as on-premises, in the cloud, and/ or at the edge. This PDF is only licensed for individual use when downloaded from forrester.com or reprints.forrester.com. All other distribution prohibited. FORRESTER.COM FOR APPLICATION DEVELOPMENT & DELIVERY PROFESSIONALS The Forrester Wave™: Streaming Analytics, Q3 2019 The 11 Providers That Matter Most And How They Stack Up by Mike Gualtieri with Srividya Sridharan and Robert Perdoni September 23, 2019 Table Of Contents Related Research Documents 2 Enterprises Must Take A Streaming-First The Future Of Machine Learning Is Unstoppable Approach To Analytics Predictions 2019: Artificial Intelligence 3 Evaluation Summary Predictions 2019: Business Insights 6 Vendor Offerings 6 Vendor Profiles Leaders Share reports with colleagues.
    [Show full text]
  • Scalable and Flexible Middleware for Dynamic Data Flows
    SCALABLEANDFLEXIBLEMIDDLEWAREFORDYNAMIC DATAFLOWS stephan boomker Master thesis Computing Science Software Engineering and Distributed Systems Primaray RuG supervisor : Prof. Dr. M. Aiello Secondary RuG supervisor : Prof. Dr. P. Avgeriou Primary TNO supervisor : MSc. E. Harmsma Secondary TNO supervisor : MSc. E. Lazovik August 16, 2016 – version 1.0 [ August 16, 2016 at 11:47 – classicthesis version 1.0 ] Stephan Boomker: Scalable and flexible middleware for dynamic data flows, Master thesis Computing Science, © August 16, 2016 [ August 16, 2016 at 11:47 – classicthesis version 1.0 ] ABSTRACT Due to the concepts of Internet of Things and Big data, the traditional client-server architecture is not sufficient any more. One of the main reasons is wide range of expanding heterogeneous applications, data sources and environments. New forms of data processing require new architectures and techniques in order to be scalable, flexible and able to handle fast dynamic data flows. The backbone of all those objects, applications and users is called the middleware. This research goes about designing and implementing a middle- ware by taking into account different state of the art tools and tech- niques. To come up to a solution which is able to handle a flexible set of sources and models across organizational borders. At the same time it is de-centralized, distributed and, although de-central able to perform semantic based system integration centrally. This is accom- plished by introducing of an architecture containing a combination of data integration patterns, semantic storage and stream processing patterns. A reference implementation is presented of the proposed architec- ture based on Apache Camel framework. This prototype provides the ability to dynamically create and change flexible and distributed data flows during runtime.
    [Show full text]
  • Big Data Analysis Using Hadoop Lecture 4 Hadoop Ecosystem
    1/16/18 Big Data Analysis using Hadoop Lecture 4 Hadoop EcoSystem Hadoop Ecosytems 1 1/16/18 Overview • Hive • HBase • Sqoop • Pig • Mahoot / Spark / Flink / Storm • Hadoop & Data Management Architectures Hive 2 1/16/18 Hive • Data Warehousing Solution built on top of Hadoop • Provides SQL-like query language named HiveQL • Minimal learning curve for people with SQL expertise • Data analysts are target audience • Ability to bring structure to various data formats • Simple interface for ad hoc querying, analyzing and summarizing large amountsof data • Access to files on various data stores such as HDFS, etc Website : http://hive.apache.org/ Download : http://hive.apache.org/downloads.html Documentation : https://cwiki.apache.org/confluence/display/Hive/LanguageManual Hive • Hive does NOT provide low latency or real-time queries • Even querying small amounts of data may take minutes • Designed for scalability and ease-of-use rather than low latency responses • Translates HiveQL statements into a set of MapReduce Jobs which are then executed on a Hadoop Cluster • This is changing 3 1/16/18 Hive • Hive Concepts • Re-used from Relational Databases • Database: Set of Tables, used for name conflicts resolution • Table: Set of Rows that have the same schema (same columns) • Row: A single record; a set of columns • Column: provides value and type for a single value • Can can be dived up based on • Partitions • Buckets Hive – Let’s work through a simple example 1. Create a Table 2. Load Data into a Table 3. Query Data 4. Drop a Table 4 1/16/18
    [Show full text]
  • Researching Algorithmic Institutions Essay
    Researching Algorithmic Institutions RESEARCHING ALGORITHMIC governance produces an essentially harnessed to the pursuit of procedures experimental condition of institutionality. That and realization of rules. Experiments lend INSTITUTIONS which becomes available for ‘disruption’ or themselves to the goal-oriented world of Liam Magee and Ned Rossiter ‘innovation’ — both institutional encodings — algorithms. As such, the invention of new Like any research centre that today is equally prescribed within silicon test-beds institutional forms and practices would seem 3 investigates the media conditions of social that propose limits to political possibility. antithetical to experiments in algorithmic organization, the Institute for Culture and Experiments privilege the repeatability and governance. Yet what if we consider Society modulates functional institutional reproducibility of action. This is characteristic experience itself as conditioned and governance with what might be said to be, of algorithmic routines that accommodate made possible by experiments in operatively and with a certain conscientious variation only through the a priori of known algorithmic governance? attention to method, algorithmic experiments. statistical parameters. Innovation, in other Surely enough, the past few decades have In this essay we convolve these terms. words, is merely a variation of the known seen a steady transformation of many As governance moves beyond Weberian within the horizon of fault tolerance. institutional settings. There are many studies proceduralism toward its algorithmic Experiments in algorithmic governance that account for such change as coinciding automation, research life itself becomes are radically dissimilar from the experience with and often directly resulting from the ways subject to institutional experimentation. of politics and culture, which can be in which neoliberal agendas have variously Parametric adjustment generates sine wave- understood as the constitutive outside of impacted organizational values and practices.
    [Show full text]
  • CIF21 Dibbs: Middleware and High Performance Analytics Libraries for Scalable Data Science
    NSF14-43054 start October 1, 2014 Datanet: CIF21 DIBBs: Middleware and High Performance Analytics Libraries for Scalable Data Science • Indiana University (Fox, Qiu, Crandall, von Laszewski), • Rutgers (Jha) • Virginia Tech (Marathe) • Kansas (Paden) • Stony Brook (Wang) • Arizona State(Beckstein) • Utah(Cheatham) Overview by Gregor von Laszewski April 6 2016 http://spidal.org/ http://news.indiana.edu/releases/iu/2014/10/big-data-dibbs-grant.shtml http://www.nsf.gov/awardsearch/showAward?AWD_ID=1443054 04/6/2016 1 Some Important Components of SPIDAL Dibbs • NIST Big Data Application Analysis: features of data intensive apps • HPC-ABDS: Cloud-HPC interoperable software with performance of HPC (High Performance Computing) and the rich functionality of the commodity Apache Big Data Stack. – Reservoir of software subsystems – nearly all from outside project and mix of HPC and Big Data communities – Leads to Big Data – Simulation - HPC Convergence • MIDAS: Integrating Middleware – from project • Applications: Biomolecular Simulations, Network and Computational Social Science, Epidemiology, Computer Vision, Spatial Geographical Information Systems, Remote Sensing for Polar Science and Pathology Informatics. • SPIDAL (Scalable Parallel Interoperable Data Analytics Library): Scalable Analytics for – Domain specific data analytics libraries – mainly from project – Add Core Machine learning Libraries – mainly from community – Performance of Java and MIDAS Inter- and Intra-node • Benchmarks – project adds to community; See WBDB 2015 Seventh Workshop
    [Show full text]
  • Issues at the Intersection of AI, Streaming, HPC, Data Centers And
    Issues at the intersection of AI, Streaming, HPC, Data-centers and the Edge NITRD Middleware and Grid Interagency Coordination Team (MAGIC) Geoffrey Fox 1 April 2020 Digital Science Center, Indiana University [email protected], http://www.dsc.soic.indiana.edu/ Digital Science Center AI, Streaming, HPC 1 Some Simple Observations • Consider Science Research Benchmarks in MLPerf • Enhance collaboration between Industry and Research; HPC and MLPerf MLSys communities • Support common environments from Edge to Cloud and HPC systems • Huge switch to Deep Learning for Big Data • Many new algorithms to be developed • Deep Learning for (Geospatial) Time Series (staple of the edge) incredibly promising: obvious relevance to Covid-19 studies • Examples • Inference at the edge • Fusion instabilities • Ride-hailing • Racing Cars • Images • Earthquakes • Solving ODE’s • Particle Physics Events • Timely versus real-time (throughput versus latency); both important Digital Science Center AI, Streaming, HPC 2 Sam,bo!"~va ....... H SIGOPT skymiz•e ®·,,.,· - SiMa"1 MLPerf Consortium Deep Learning Benchmarks Rpa2a1 Sambanova Samsung S.LSI Sigopt SiMaAI Skymizer Supermicro Tencent synOPSYS" TTE.NSYR TERAa,'NE Q>r.. .._, ... ..,. ~ VHind Companies •m verifAI Some Relevant Working Groups Synopsys Tencent Tensyr Teradyne Transpire Ventures VerifAI VMind , Al labs.tw •• 11--.u••--· a-- arm • Training vmware ,( volley.com VV/\V:. £ XILINX. Al Labs.tw Alibaba AMO Andes Technology Aon Devices Arm Baidu • Inference (Batch and Streaming) VMware Volley Wave Computing Wiwynn WekalO Xilinx • TinyML (embedded) !.!!P.l!!'.!!!!!! cadence' CALYPSO {in]i!ur f erebras CEVA • Deep Learning for Time Series Resea rchers from BAAi Cadence Calypso Al Centaur Technology Cerebras Ceva Cirrus • Power ... dii .. 1,.
    [Show full text]
  • Apache Beam: Portable and Evolutive Data-Intensive Applications
    Apache Beam: portable and evolutive data-intensive applications Ismaël Mejía - @iemejia Talend Who am I? @iemejia Software Engineer Apache Beam PMC / Committer ASF member Integration Software Big Data / Real-Time Open Source / Enterprise 2 New products We are hiring ! 3 Introduction: Big data state of affairs 4 Before Big Data (early 2000s) The web pushed data analysis / infrastructure boundaries ● Huge data analysis needs (Google, Yahoo, etc) ● Scaling DBs for the web (most companies) DBs (and in particular RDBMS) had too many constraints and it was hard to operate at scale. Solution: We need to go back to basics but in a distributed fashion 5 MapReduce, Distributed Filesystems and Hadoop ● Use distributed file systems (HDFS) to scale data storage horizontally ● Use Map Reduce to execute tasks in parallel (performance) ● Ignore strict model (let representation loose to ease scaling e.g. KV stores). (Prepare) Great for huge dataset analysis / transformation but… Map (Shuffle) ● Too low-level for many tasks (early frameworks) ● Not suited for latency dependant analysis Reduce (Produce) 6 The distributed database Cambrian explosion … and MANY others, all of them with different properties, utilities and APIs 7 Distributed databases API cycle NewSQL let's reinvent NoSQL, because our own thing SQL is too limited SQL is back, because it is awesome 8 (yes it is an over-simplification but you get it) The fundamental problems are still the same or worse (because of heterogeneity) … ● Data analysis / processing from systems with different semantics ● Data integration from heterogeneous sources ● Data infrastructure operational issues Good old Extract-Transform-Load (ETL) is still an important need 9 The fundamental problems are still the same "Data preparation accounts for about 80% of the work of data scientists" [1] [2] 1 Cleaning Big Data: Most Time-Consuming, Least Enjoyable Data Science Task 2 Sculley et al.: Hidden Technical Debt in Machine Learning Systems 10 and evolution continues ..
    [Show full text]
  • Spring 2020 1/21
    CS 591 K1: Data Stream Processing and Analytics Spring 2020 1/21: Introduction Vasiliki (Vasia) Kalavri [email protected] Vasiliki Kalavri | Boston University 2020 Course Information • Instructor: Vasiliki Kalavri • Office: MCS 206 • Contact: [email protected] • Course Time & Location: Tue,Thu 9:30-10:45, MCS B33 • Office Hours: Tue,Thu 11:00-12:30, MCS 206 2 Vasiliki Kalavri | Boston University 2020 Announcements, updates, discussions • Website: vasia.github.io/dspa20 • Syllabus: /syllabus.html • Class schedule: /lectures.html • including today’s slides • Piazza: piazza.com/bu/spring2020/cs591k1/home • For questions & discussions • Blackboard: learn.bu.edu/... • For quizzes, assignment announcements & submissions 3 Vasiliki Kalavri | Boston University 2020 What is this course about? The design Operator semantics and architecture of modern Window optimizations distributed streaming Systems Filtering, counting, sampling Graph streaming algorithms Architecture and design Scheduling and load management Scalability and elasticity Fundamental Algorithms Fault-tolerance and guarantees for representing, summarizing, State management and analyzing data streams 4 Vasiliki Kalavri | Boston University 2020 Tools Apache Flink: flink.apache.org Apache Kafka: kafka.apache.org Apache Beam: beam.apache.org Google Cloud Platform: cloud.google.com 5 Vasiliki Kalavri | Boston University 2020 Outcomes At the end of the course, you will hopefully: • know when to use stream processing vs other technology • be able to comprehensively compare features and processing
    [Show full text]
  • Code Smell Prediction Employing Machine Learning Meets Emerging Java Language Constructs"
    Appendix to the paper "Code smell prediction employing machine learning meets emerging Java language constructs" Hanna Grodzicka, Michał Kawa, Zofia Łakomiak, Arkadiusz Ziobrowski, Lech Madeyski (B) The Appendix includes two tables containing the dataset used in the paper "Code smell prediction employing machine learning meets emerging Java lan- guage constructs". The first table contains information about 792 projects selected for R package reproducer [Madeyski and Kitchenham(2019)]. Projects were the base dataset for cre- ating the dataset used in the study (Table I). The second table contains information about 281 projects filtered by Java version from build tool Maven (Table II) which were directly used in the paper. TABLE I: Base projects used to create the new dataset # Orgasation Project name GitHub link Commit hash Build tool Java version 1 adobe aem-core-wcm- www.github.com/adobe/ 1d1f1d70844c9e07cd694f028e87f85d926aba94 other or lack of unknown components aem-core-wcm-components 2 adobe S3Mock www.github.com/adobe/ 5aa299c2b6d0f0fd00f8d03fda560502270afb82 MAVEN 8 S3Mock 3 alexa alexa-skills- www.github.com/alexa/ bf1e9ccc50d1f3f8408f887f70197ee288fd4bd9 MAVEN 8 kit-sdk-for- alexa-skills-kit-sdk- java for-java 4 alibaba ARouter www.github.com/alibaba/ 93b328569bbdbf75e4aa87f0ecf48c69600591b2 GRADLE unknown ARouter 5 alibaba atlas www.github.com/alibaba/ e8c7b3f1ff14b2a1df64321c6992b796cae7d732 GRADLE unknown atlas 6 alibaba canal www.github.com/alibaba/ 08167c95c767fd3c9879584c0230820a8476a7a7 MAVEN 7 canal 7 alibaba cobar www.github.com/alibaba/
    [Show full text]