2-tier vs. 3-tier Architectures for Data Processing Software

Dmitriy Dorofeev, S. Shestakov
{"title":"2-tier vs. 3-tier Architectures for Data Processing Software","authors":"Dmitriy Dorofeev, S. Shestakov","doi":"10.1145/3274856.3274869","DOIUrl":null,"url":null,"abstract":"The rise of data-centric computing, NoSQL and newSQL databases with powerful scripting capabilities, popularity of REST API raise a question: is it feasible to serve clients directly from the DB, with REST API server residing inside the database? What would be the balance between data processing, application, and presentation logic for such a scenario on a server side and on a client side? In this paper we will compare 2 real-world implementations of the commercial Luxms BI analytical platform based on 2-tier and on 3-tier architecture. Our research shows that despite popularity of 3-tier architectures, in-database application server approach delivers better performance in both throughput and latency in analytical client-server application development.","PeriodicalId":373840,"journal":{"name":"Proceedings of the 3rd International Conference on Applications in Information Technology","volume":"20 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2018-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the 3rd International Conference on Applications in Information Technology","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3274856.3274869","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 2

Abstract

The rise of data-centric computing, NoSQL and newSQL databases with powerful scripting capabilities, popularity of REST API raise a question: is it feasible to serve clients directly from the DB, with REST API server residing inside the database? What would be the balance between data processing, application, and presentation logic for such a scenario on a server side and on a client side? In this paper we will compare 2 real-world implementations of the commercial Luxms BI analytical platform based on 2-tier and on 3-tier architecture. Our research shows that despite popularity of 3-tier architectures, in-database application server approach delivers better performance in both throughput and latency in analytical client-server application development.
数据处理软件的两层与三层架构
以数据为中心的计算的兴起,NoSQL和newSQL数据库具有强大的脚本功能,REST API的流行提出了一个问题:REST API服务器驻留在数据库中,直接从数据库为客户端提供服务是否可行?对于服务器端和客户端的这种场景,数据处理、应用程序和表示逻辑之间的平衡是什么?在本文中,我们将比较基于两层和三层架构的商业Luxms BI分析平台的两种实际实现。我们的研究表明,尽管三层架构很流行,但在分析客户机-服务器应用程序开发中,数据库内应用程序服务器方法在吞吐量和延迟方面提供了更好的性能。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信