170 likes | 183 Views
This paper presents a proposal for a reference architecture that combines cloud, fog, and edge computing paradigms to enable efficient and scalable big data analytics. The architecture includes an Analytical Orchestrator and Life Cycle Management for self-rescheduling and self-monitoring. The proposed architecture aims to address the challenges and shortcomings of existing technologies and provide a comprehensive solution for big data analytics in Industry 4.0.
E N D
Towards an Architecture for Big Data Analytics Leveraging Edge/Fog Paradigms ECSA, September 9–13, 2019, Paris, France Josu Díaz-de-Arcaya Raúl Miñón Ana I. Torre-Bastida
Outline • Introduction • Background • Motivation • Challenges • Our Proposal • Conclusion & Future Work
Industry 4.0 Introduction
Industry 4.0: Enablers Introduction Big Data IoT Cloud Computing a style of computing in which scalable and elastic IT-enabled capabilities are delivered as a service using Internet technologies. Gartner is high-volume, high-velocity and/or high-variety information assets that demand cost-effective, innovative forms of information processing that enable enhanced insight, decision making, and process automation. Gartner is the network of physical objects that contain embedded technology to communicate and sense or interact with their internal states or the external environment. Gartner
Big Data Architectures Background In order to deal with Big Data stringent requirements two leading architectures arose Lambda Kappa https://www.oreilly.com/ideas/applying-the-kappa-architecture-in-the-telco-industry
Computing models Challenges An IT infrastructure which need to widen through cloud fog and edge computing paradigms
Resource Negotiators Challenges 2015 2006 2010 • Shortcomings • Existing technologies are cluster based. • They are not specific for Analytical Workloads, nor do they understand its phases.
Horizontal Orchestrators & MLAAS Challenges Hadoop YARN / Mesos / Kubernetes Orchestrator node_1 node_0 node_2 node_N Machine Learning into production MLaaS
Motivation Motivation We have identified the need for a new reference architecture that includes all the resources in the different layers and should be capable of self-rescheduling and self-monitoring
General Reference Architecture Definition OurProposal
Implementation Technologies Our proposal
Vertical Orchestrator Out proposal Cloud This is where we are going to focus our research and development efforts Fog AnalyticOrchestrator and Life Cycle Management Edge
Our contribution Analytical Orchestrator Module Catalogue Analytical Pipeline Cost Estimation Analytical Pipelines Validation Agent 1 Kernel Agent 2 SCM Agent 3 Analytical Pipeline Orchestration Analytical Pipeline Monitoring Agent N
Our contribution Analytical Orchestrator Module
Conclusion & Future Work Our Contributions Cloud • Reference Architecture that encompasses Cloud & Fog & Edge • We will focus on the Analytic Orchestrator and Life Cycle Management Fog AO&LFM Edge
Future Work Conclusion & Future Work Cloud • In order to implement the Orchestrator: • Define the available resources and the pipelines in detail (PMML, PFA, …). • Optimisation of the pipeline deployment plan will be implemented using an algorithm based on JMETAL framework. Fog AO&LFM Edge