Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
iamlintaoz
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
1.
▲
by
iamlintaoz
8mo ago
This is not true at all. China’s education system is nationally standardized. Although economic development is uneven with far greater investment concentrated in major cities than inland regions, the structure of education itself is consist
2.
▲
by
iamlintaoz
8mo ago
It’s true that learning Chinese as an adult—especially if you come from an English or other European language background—can be extremely challenging. I have several colleagues who have lived in Beijing for more than a decade, are married t
3.
▲
by
iamlintaoz
9mo ago
The disk storage EloqKV uses (EloqStore [1]) is optimized for batch updates because the upper Data Substrate layer manages buffering and the Write-Ahead Log (WAL), absorbing writes and guaranteeing durability. When durability is not require
4.
▲
by
iamlintaoz
9mo ago
If you need so many tricks to support the infra, it will eventually come back to bite you. I am pretty sure that Google in year 2000 could have supported their workloads with existing technologies (Yahoo could, and it was a much larger comp
5.
▲
Don't Split My Data: I Will Use a Database (Not PostgreSQL) for My Data Needs
(eloqdata.com)
1 points
by
iamlintaoz
11mo ago
|
1 comments
6.
▲
by
iamlintaoz
1y ago
These are great questions. I appreciate you carefully reading through the documents. For the first question, we have detailed benchmark on EloqKV, with the same architecture (but with Redis API) in our blog, and we will soon publish more ab
7.
▲
by
iamlintaoz
1y ago
That's exactly the reason. S3 is better in almost all aspects compared with EBS, except the performance part, and I am glad that our Data Substrate technology solved this issue gracefully [1]. As for the compatibility, we are leveragin
8.
▲
by
iamlintaoz
1y ago
For full transparency, I am the CEO of EloqData and I am happy to answer any questions you have. EloqDoc has been open-sourced for awhile, and we are glad to announce that the current code is stable for you to test on your workload.
9.
▲
by
iamlintaoz
1y ago
Thank you so much for reporting this! My local testing on Chrome privacy mode was fine, but we will definitely prioritize checking and fixing the issue in Firefox's Strict Privacy Mode.
10.
▲
by
iamlintaoz
1y ago
That is right. We leverage some of the AGPL MongoDB code for the parser, as indicated by the License. Our own code can be licensed differently, see a previous discussion on Hacker News [1]. The Mongo API are reasonably stable over the last
11.
▲
by
iamlintaoz
1y ago
That’s correct. FerretDB and DocumentDB both pursue PostgreSQL-based document models. EloqDoc follows a fundamentally different architectural path. Instead of executing in Postgres, we leverage the existing MongoDB parser and executor to en
12.
▲
by
iamlintaoz
1y ago
Yes, this is exactly the typical use case where EloqDoc shines. Our auto-tiering feature allows you to manage a massive database (e.g., 5TB+) primarily on cheap, durable object storage (like S3), which is already built for cross-AZ replicat
13.
▲
Show HN: EloqDoc: MongoDB-compatible doc DB with object storage as first citizen
(github.com)
46 points
by
iamlintaoz
1y ago
|
18 comments
14.
▲
by
iamlintaoz
1y ago
Thank you. Indeed we do already have several large multi-national companies using EloqKV in their production environments. Please contact us if you have any further questions. Moreover, we would be really interested to hear more details abo
15.
▲
by
iamlintaoz
1y ago
Great question. Currently, the database landscape is very fragmented. We are faced with a multitude of database choices (different ACID guarantees, data modalities, scalability, and so on). Data pipeline become very complicated, and we beli
16.
▲
by
iamlintaoz
1y ago
TiKV is a great project and we have a lot of respect for their work. EloqKV is based on a very different architecture [1], and we also have MySQL compatible [2] and MongoDB compatible [3] databases build on top of the same architecture. The
17.
▲
by
iamlintaoz
1y ago
That’s right. You can simply choose GPL and ignore the AGPL part for EloqKV. The reason we use both is that, in other projects, we need to support both GPL and AGPL. EloqKV and all its dependencies are either developed by us or licensed und
18.
▲
by
iamlintaoz
1y ago
The reason is because we use a layer (our main innovation) called DataSubstrate to build modular databases that support distributed transactions [1]. Because we use some MariaDB code (GPLv2) and some MongoDB code (AGPLv3) in our other proje
19.
▲
by
iamlintaoz
1y ago
Really appreciate it. I am the CEO of EloqData. We submitted the ShowHN about a year ago [1]. Since then we made a lot of progress, much of the work is based on the feedback from the great HN community, including: 1) Open Source (GPL and AG
20.
▲
by
iamlintaoz
1y ago
Why? Honestly, there are already tons of Model-as-a-Service (MaaS) platforms out there—big names like AWS Bedrock and Azure AI Foundry, plus a bunch of startups like Groq and fireflies.ai. I’m just not seeing what makes Cerebrium stand out
21.
▲
by
iamlintaoz
2y ago
You're absolutely right—discussing the CAP theorem is essential for any distributed storage system. We are preparing a detailed blog post to cover the implications of CAP in our system. In brief, our system generally aligns with PC
22.
▲
by
iamlintaoz
2y ago
Thank you for the insightful reply. I agree, Redis's transaction API ("MULTI/EXEC/DISCARD/WATCH") is challenging compared to SQL's familiar "START/COMMIT/ROLLBACK," and it has key limit
23.
▲
by
iamlintaoz
2y ago
Thank you, Andy! This is Jeff, CEO and Chief Architect of EloqData. It's a great honor for us to have THE Andy Pavlo join the discussion on our first HN submission. If I remember correctly, NuoDB uses a shared cache with a cache cohere