Every category where a model named Apache HBase for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
NoSQL databases	Data platform	0%	48 of 72	31%	13	criticized challenger

Movement

This is the first edition on this tier, so no move can be computed for Apache HBase yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated Apache HBase across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	Mention	Negative	Labels
Claude Haiku 4.5	0	1	1
GPT-5.4 mini	0	0	0
Gemini 3.5 Flash	0	1	1
Perplexity Sonar	1	0	1
Grok 4.1 Fast	0	0	0
Mistral Small	1	1	2
DeepSeek V4 Flash	2	1	3
Llama 4 Maverick	1	0	1
Qwen 3.7 Flash	2	0	2
Kimi K2	0	0	0
GLM 4.7 FlashX	1	0	1
MiniMax M2.5	1	0	1

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct0 labelsNone

Paraphrase0 labelsNone

Comparative5 labelsNone

Budget-constrained0 labelsNone

Scale-constrained5 labelsNone

Negative17 labelsNone

First choiceAlternativeMentionNegative27 labels in all, every segment counted; 0 of the 0 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

No positive label carried a quote.

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

“HBase has similar capabilities to Cassandra but is unable to cope with high loads... and is also the worst database in terms of robustness” Claude Haiku 4.5 · NoSQL · negative prompt · hard negative

“The databases most people should genuinely steer clear of today are the legacy/complex ones (HBase, Riak)” DeepSeek V4 Flash · NoSQL · negative prompt · hard negative

“Apache HBase (Avoid for new projects): ... maintaining a Hadoop/HBase stack is an operational nightmare” Gemini 3.5 Flash · NoSQL · negative prompt · hard negative

“Requires significant operational expertise ... can be overkill for smaller projects” Mistral Small · NoSQL · negative prompt · soft negative

Named alongside

The products named in the same answers as Apache HBase, over the 27 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Apache HBase was named but was not.

ProductSame answerTook the first choice insteadHead to head

MongoDB26 of 278Not in the top three

Apache Cassandra26 of 271Not in the top three

Redis23 of 271Not in the top three

Amazon DynamoDB20 of 273Not in the top three

Neo4j19 of 271Not in the top three

Couchbase16 of 270Not in the top three

ScyllaDB11 of 270Not in the top three

PostgreSQL9 of 273Not in the top three

Azure Cosmos DB9 of 271Not in the top three

Apache CouchDB9 of 270Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Apache HBase. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 17 of the 27 answers that named Apache HBase and are not a share of its labels.

Domains cited

alex-klaus.com8

geeksforgeeks.org8

voltactivedata.com8

reddit.com7

aws.amazon.com6

dataversity.net6

mongodb.com6

aerospike.com5

designgurus.io5

journalofbigdata.springeropen.com5

Sixty-four of the sixty-four domain citations in answers naming Apache HBase came from somebody else's page.

Pages cited

alex-klaus.com/reasons-not-to-nosql8

voltactivedata.com/blog/2021/10/nosql-due-diligence-part-18

aws.amazon.com/smart-business/resources-for-smb/sql-vs-nosql6

designgurus.io/course-play/grokking-system-design-fundamentals/doc/nosql-databases5

journalofbigdata.springeropen.com/articles/10.1186/s40537-015-0025-05

dataversity.net/articles/nosql-databases-advantages-and-disadvantages4

geeksforgeeks.org/nosql/challenges-of-nosql4

aerospike.com/blog/ten-best-nosql-cloud-databases3

Pages are listed as the models cited them.

Names read as Apache HBase

What the judge wrote, as written, with how often. The vendor table decides that these count as Apache HBase; a claim can dispute any of them.

HBase 10

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Apache HBase's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Apache HBase, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at apache.org is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.