HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
stoneatom
stonedb
C++2022–2022
stoneatom / stonedb

stonedb

https://github.com/Shannon-Data/ShannonBase

Data & Databases
Explore on GitHubRead Hacker News discussions
3Distinct people
5Mentions
0Explicit recommenders
884GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

https://github.com/Shannon-Data/ShannonBase

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week5 dated mentions

Observed mentions: 2022-07-06 05:50:45 UTC to 2022-12-14 08:26:35 UTC. Weeks start Monday, UTC.

01232022-07-04 00:00:00 UTC to 2022-07-11 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 commentsJul 42022-07-11 00:00:00 UTC to 2022-07-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-18 00:00:00 UTC to 2022-07-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-25 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-01 00:00:00 UTC to 2022-08-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-08 00:00:00 UTC to 2022-08-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-15 00:00:00 UTC to 2022-08-22 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2022-08-22 00:00:00 UTC to 2022-08-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-29 00:00:00 UTC to 2022-09-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-05 00:00:00 UTC to 2022-09-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-12 00:00:00 UTC to 2022-09-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-19 00:00:00 UTC to 2022-09-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 192022-09-26 00:00:00 UTC to 2022-10-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-03 00:00:00 UTC to 2022-10-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-10 00:00:00 UTC to 2022-10-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-17 00:00:00 UTC to 2022-10-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-24 00:00:00 UTC to 2022-10-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-31 00:00:00 UTC to 2022-11-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-07 00:00:00 UTC to 2022-11-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-14 00:00:00 UTC to 2022-11-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-21 00:00:00 UTC to 2022-11-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-28 00:00:00 UTC to 2022-12-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-05 00:00:00 UTC to 2022-12-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-12 00:00:00 UTC to 2022-12-19 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 12

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 42022-07-04 00:00:00 UTC2022-07-11 00:00:00 UTC321
Jul 112022-07-11 00:00:00 UTC2022-07-18 00:00:00 UTC000
Jul 182022-07-18 00:00:00 UTC2022-07-25 00:00:00 UTC000
Jul 252022-07-25 00:00:00 UTC2022-08-01 00:00:00 UTC000
Aug 12022-08-01 00:00:00 UTC2022-08-08 00:00:00 UTC000
Aug 82022-08-08 00:00:00 UTC2022-08-15 00:00:00 UTC000
Aug 152022-08-15 00:00:00 UTC2022-08-22 00:00:00 UTC110
Aug 222022-08-22 00:00:00 UTC2022-08-29 00:00:00 UTC000
Aug 292022-08-29 00:00:00 UTC2022-09-05 00:00:00 UTC000
Sep 52022-09-05 00:00:00 UTC2022-09-12 00:00:00 UTC000
Sep 122022-09-12 00:00:00 UTC2022-09-19 00:00:00 UTC000
Sep 192022-09-19 00:00:00 UTC2022-09-26 00:00:00 UTC000
Sep 262022-09-26 00:00:00 UTC2022-10-03 00:00:00 UTC000
Oct 32022-10-03 00:00:00 UTC2022-10-10 00:00:00 UTC000
Oct 102022-10-10 00:00:00 UTC2022-10-17 00:00:00 UTC000
Oct 172022-10-17 00:00:00 UTC2022-10-24 00:00:00 UTC000
Oct 242022-10-24 00:00:00 UTC2022-10-31 00:00:00 UTC000
Oct 312022-10-31 00:00:00 UTC2022-11-07 00:00:00 UTC000
Nov 72022-11-07 00:00:00 UTC2022-11-14 00:00:00 UTC000
Nov 142022-11-14 00:00:00 UTC2022-11-21 00:00:00 UTC000
Nov 212022-11-21 00:00:00 UTC2022-11-28 00:00:00 UTC000
Nov 282022-11-28 00:00:00 UTC2022-12-05 00:00:00 UTC000
Dec 52022-12-05 00:00:00 UTC2022-12-12 00:00:00 UTC000
Dec 122022-12-12 00:00:00 UTC2022-12-19 00:00:00 UTC110

What Hacker News says

5 sources
Bright_Li·Dec 14, 2022Submission

Show HN: An Open-Source MySQL HTAP Database for OLTP, Real-Time Analytics

After the release of StoneDB V1.0 on GitHub, we have received lots of feedback from our community members and users. As shown in the TPC-H test reports, StoneDB V1.0 provides 10 to 100 times higher performance than MySQL, with only one tenth the total cost of ownership (TCO). Though StoneDB V1.0 provides inspiring performance, it still has some drawbacks that are rooted in its design, including long execution time for TPC-H query 16, unsatisfying performance in processing transactional workloads, and comparatively long latency in populating latest changes to analytics workloads. Therefore, we are redesigning StoneDB to eliminate these problems in our next version — StoneDB V2.0. StoneDB V2.0 will be based on MySQL 8.0. It aims to achieve at least 10 times higher query performance on TPC-H than that of V1.0, with a more concise architectur
Read the rest
e and a query optimizer that can intelligently offload query workloads to corresponding storage engines. The design philosophy of StoneDB V2.0 is modularity and performance-cost balance. The following outlines the new features that will be implemented in StoneDB V2.0. To learn details about each feature, see the relevant chapter. StoneDB V2.0 will still be an open source project, which is a counterpart of close source service, MySQL Heatwave. At first, an in-memory column-based engine (IMCE) will be used. Secondly, a cost-based query engine will be developed to automatically offload transactional and analytics workloads. Thirdly, StoneDB V2.0 will provide a vectorized execution engine and support massive parallel processing. In this way, the execution performance of StoneDB V2.0 will be at least ten times as that of StoneDB V1.0. StoneDB will load the data into memory from InnoDB, just the same as MySQL Heatwave.
1 points · Open discussion
Bright_Li·Aug 18, 2022Submission

Show HN: StoneDB—A Real-Time HTAP Database Based on the MySQL Kernel

StoneDB is an open-source hybrid transaction/analytical processing (HTAP) database designed and developed by StoneAtom based on the MySQL kernel. It is the first database of this type launched in China. StoneDB can be seamlessly switched from MySQL. It provides features such as optimal performance and real-time analytics, offering you a one-stop solution to process online transaction processing (OLTP), online analytical processing (OLAP), and HTAP workloads. StoneDB is fully compatible with the MySQL 5.6 and 5.7 protocols, the MySQL ecosystem, and common MySQL features and syntaxes. Tools and clients in the MySQL ecosystem, such as Navicat, Workbench, mysqldump, and mydumper, can be directly used on StoneDB. In addition, all workloads on StoneDB can be run on MySQL. StoneDB is optimized for OLAP applications. StoneDB that runs on a common
Read the rest
server can process complex queries on tens of billions of data records, while ensuring high performance. Compared to databases that use MySQL Community Edition, StoneDB is at least 10 times faster in processing queries. StoneDB uses the Knowledge Grid technology and a column-based storage engine. The column-based storage engine is designed for OLAP applications and uses techniques such as column-based storage, Knowledge Grid-based filtering, and high-efficiency data compression. With such storage engine, StoneDB ensures the high performance of application systems and reduces the total cost of ownership (TCO).
4 points · Open discussion
YangWilly·Jul 6, 2022Submission

StoneDB – A real-time HTAP database built on MySQL

StoneDB is an open-source hybrid transaction/analytical processing (HTAP) database based on the MySQL kernel. StoneDB can be seamlessly switched from MySQL. It provides features such as optimal performance and real-time analytics, offering you a one-stop solution to process online transaction processing (OLTP), online analytical processing (OLAP), and HTAP workloads. Homepage: https://stonedb.io/ Github repo: https://github.com/stoneatom/stonedb
6 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.