问题描述
任何人都可以建议将HBase作为基于Web的应用程序的主要数据源是一个好主意吗?我主要关心的是HBase对查询的回应时间。是否有可能进行亚秒级响应?编辑:关于应用程序本身的更多细节。
- 数据量: 〜500GB的文本数据,预计将很快达到1TB
- 使用该应用程序的并发用户数量:最多50个
该应用将用于呈现关于存储在HBase中的数据的报告,例如最近24小时发生关键字X的次数。对于来自该应用程序的约80%的请求,我将知道确切的关键,20%将被扫描(我正在研究HBase架构设计相关主题以使其运行速度很快)
您可以将HBase用作web应用程序的后端(请参阅Gap的演示文稿或eBay的介绍)。
当您提到自己时,重点是要获得正确的模式和关键设计
Can anyone advise if it is a good idea to have HBase as primary data source for web-based application? My primary concern is HBase's response time to queries. Is it possible to have sub-second response?
edit: more details about the app itself.
- Amount of data: ~500GB of text data, expect to reach 1TB soon
- Number of concurrent users using the app: up to 50
The app will be used to present reports about data stored in HBase, like how many times keyword "X" occured in last 24h. For ~80% of requests from that app I will know the exact key, 20% will be scans (I'm looking into HBase schema design related topics to make it run fast)
You can use HBase as a backend for a webapp (see for example Gap's presentation here or EBay's presentation here).
As you noted yourself the point is to get the right schema and key design
这篇关于HBase作为网络应用后端的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!