Proceedings of the 13th International Conference on Software Technologies 2018
DOI: 10.5220/0006825408330840
|View full text |Cite
|
Sign up to set email alerts
|

Non-functional Requirements for Real World Big Data Systems - An Investigation of Big Data Architectures at Facebook, Twitter and Netflix

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
15
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
3
1

Relationship

2
2

Authors

Journals

citations
Cited by 4 publications
(15 citation statements)
references
References 9 publications
0
15
0
Order By: Relevance
“…Also, as new data are continuously added via the data stream that gets collected daily, the model makes use of the speed layer and batch layer of big data technologies for data processing. Finally, the output will be used for reinforcement learning in the servicing layer of the big data architecture that caters to both functional and non-functional requirements [39].…”
Section: Use Case Of Proposed Model For Smart Home Automationmentioning
confidence: 99%
“…Also, as new data are continuously added via the data stream that gets collected daily, the model makes use of the speed layer and batch layer of big data technologies for data processing. Finally, the output will be used for reinforcement learning in the servicing layer of the big data architecture that caters to both functional and non-functional requirements [39].…”
Section: Use Case Of Proposed Model For Smart Home Automationmentioning
confidence: 99%
“…Facebook, Twitter and Netflix) with the purpose of understanding nonfunctional requirements for real-world big data systems. The selection criteria for these companies, methodology and results of this evaluation are explained in a separate publication [29]; RO2 -based on the findings in RO1, propose a new reference architecture based on industry's best practices and focused on vendor lock-in mitigation; RO3 -develop a prototype, based on a case study, to enable the empirical evaluation of the proposed reference architecture; RO4: to identify and implement a set of relevant performance metrics for the prototype in RO3; RO5 -to design and execute distinct sets of experiments to evaluate the proposed reference architecture in terms of the non-functional requirements implemented.…”
Section: Aim and Objectivesmentioning
confidence: 99%
“…Finally, the evaluation of Maier's reference architecture was performed by analysing the real-world big data implementations of Facebook, LinkedIn and Oracle and retrofitting them to the reference architecture proposed [50]. While this research did perform a similar investigation of real-world big data implementations [29], its purpose was not to evaluate the MC-BDP proposal, but to gather requirements for it. The evaluation of MC-BDP was performed through a concrete case-study, with both quantitative and qualitative data collected and thoroughly analysed as part of a rigorous scientific process described in Section 3.…”
Section: Related Literature Reviewmentioning
confidence: 99%
“…MOA provides a microservice-oriented modelling approach for designing and implementing the interaction and communication among software service layers to support information sharing among different stakeholders for providing smart services in an ITS. We identify the key software service requirements of our proposed microservice-oriented modelling for smart transportation and analytics [37,38].…”
Section: Service-driven Modelling For Itssmentioning
confidence: 99%
“…Typically, ITSs should be capable of scaling horizontally and handling large amount of traffic coming from several heterogeneous data sources such as IoT devices, smartphones, cameras, machine logs, and social media [38,45]. There are ten non-functional microservice performance requirements in the context of designing contemporary data architectures for intelligent systems: Batch data, stream data, late and out-of-order data, processing guarantees, integration and extensibility, distribution and scalability, cloud support and elasticity, fault-tolerance, flow control, and flexibility and technology agnosticism [38]. Conventional big data systems that rely on MapReduce jobs and batch ETL cannot be used because of high latency in ingesting new data [46].…”
Section: Non-functional Microservice Performance Requirements Of Itssmentioning
confidence: 99%