NHacker Next
login
▲Timescale Is Now TigerDatatigerdata.com
139 points by pbowyer 23 hours ago | 100 comments
Loading comments...
smokel 7 hours ago [-]
> There are no more “SQL vs. NoSQL” debates. MongoDB, Cassandra, InfluxDB, and other NoSQL databases are seen as technical dead ends. Snowflake and Databricks are acquiring PostgreSQL companies. No one talks about Hadoop. The Lakehouse has won.

That's quite some statement. Boy, would I have loved to live in a world where marketing rhetoric and scientific opinion were easier to distinguish.

mellosouls 1 hours ago [-]
Also linking to an old HN comment to gloat about how wrong the doubters were is not a good look.

There's an element of immaturity in the style that they should probably work on.

inamorty 32 minutes ago [-]
I concur, the tone is very off-putting.
sgarland 58 minutes ago [-]
Cassandra definitely isn’t dead, anyway. InfluxDB is a competitor to Timescale / TigerData, so that’s just a slam on them. I don’t think about MongoDB, other than of course the canonical video [0].

[0]: https://youtu.be/b2F-DItXtZs

baggiponte 7 hours ago [-]
Yeah they might be good but the marketing is really bold and, to a certain extent, arrogant if not outright disgusting.
suyash 1 hours ago [-]
It sounds totally illogical comment, all those technologies mentioned have only been growing in the last few years and specialised databases are disrupting old school SQL ones.
ethagnawl 10 hours ago [-]
This makes a certain amount of sense because it seems like the actual timescale DB extension/support/etc. they offer is becoming exponentially less important to their company as a result of their pgvectorscale offering. (I'm sure the post says as much.)

I did some work using pgvectorscale and their hosted offering a few months back and the product and the team were a delight to work with. I wish TigerData well.

jabiko 7 hours ago [-]
We've been using TimescaleDB/TigerData for over five years now and it has proven to be a reliable component of our project. We process and store hundreds of data points for a six-digit number of industrial robots and TimescaleDB is what makes that possible. While I can't speak for Timescale Cloud, the managed service for TimescaleDB on Azure has been rock solid.

One annoying thing is that tiered storage is not available on their Azure offering, and also in general it feels like managed service for TimescaleDB is the unloved stepchild of their offering.

But yes, I hope the team continues their amazing work, and I'm looking forward to seeing how the project develops in the future.

ramonguiu 5 hours ago [-]
@jabiko thanks for the note. Glad our product is working so well for you. re:Azure we are working on some new things :) . Feel free to drop me a message if you'd like to discuss further (ramon@tigerdata.com).
apgwoz 10 hours ago [-]
So there’s TigerData and TigerBeetle. I wish they would have chosen a different fast cat…
kajecounterhack 9 hours ago [-]
I know what you mean, but still Tiger Beetles are an insect https://en.wikipedia.org/wiki/Tiger_beetle
apgwoz 7 hours ago [-]
I thought about that, but, but it’s not the comparison of the second word, it’s the strength of the first. Read this list:

* Tiger Shark * Tiger Beetle * Tiger Data * Tiger Games * Tiger Woods * Tiger Attack * Tiger Snake * Wild Tiger

Only one stands out as not like the others. Tiger is too strong a word. The second word disappears.

pcthrowaway 8 hours ago [-]
Also WiredTiger https://en.wikipedia.org/wiki/WiredTiger
andrenotgiant 3 hours ago [-]
Don't forget Tigris https://www.tigrisdata.com/
agos 1 hours ago [-]
they even have a similar palette on their website, I could have sworn they were from the same company
alexpadula 8 hours ago [-]
WildcatDB, though uses a cheetah for the logo RocksDB uses an I believe tiger for the logo as well. Postgres with the elephant, MariaDB with the seal.
akulkarni 2 hours ago [-]
We chose the Tiger back in April 2017.

Also TigerBeetle is an insect, not a fast cat.

tao_oat 4 hours ago [-]
And TigerGraph, too!
9 hours ago [-]
orphea 3 hours ago [-]
Slightly off-topic perhaps. For my use case (both short-term and long-term storage of sensors and metrics of a small Home Assistant instance) it probably doesn't matter, but what could someone recommend? ClickHouse looks kind of neat and it doesn't appear to be difficult to admin.
Rebelgecko 28 minutes ago [-]
If you like standard SQL-y type queries, timescaledv itself is a good option. Influx is another option but it has a steeper learning curve and imo it doesn't pay off
ejs 2 hours ago [-]
Since this is a timescaleDB topic, would timescale not work? (With a basic DB and a few continuous aggregates running in the background?)
skowalak 2 hours ago [-]
At the company I work at we manage a lot of historical data with Timescale, but we have also had good results with vanilla PostgreSQL for smaller time-series-data-sets. If you are already comfortable with Postgres this might be worth a look.
suyash 1 hours ago [-]
I would go with InfluxDB, actually it's powers several Home Assistant apps behind the scene already for a reason.
conradev 7 hours ago [-]

  TigerData is bold, fast, and built to power the next era of software.
We already have a Tiger-themed database at home: https://github.com/tigerbeetle/tigerbeetle
igitur 7 hours ago [-]
When I saw the headline I immediately thought that TigerData is somehow related to the TigerBeetle.
rbaudibert 7 hours ago [-]
TIL you can have GIFs as the `og:image` and Slack and friends will render them as GIFs, actually wild
LeonM 5 hours ago [-]
I recon you mean that the GIF is animated? I tried pasting this with the article URL in Whatsapp (web), but it did not render any animation for me.

Care to elaborate on why you posted this?

aorth 16 minutes ago [-]
They learned something and wanted to share.

Did you try Slack?

3 hours ago [-]
zlib 4 hours ago [-]
Timescale is much better
koakuma-chan 2 hours ago [-]
They should have kept timescale
cakoose 7 hours ago [-]
> When we started 8 years ago, SQL databases were “old fashioned.” NoSQL was the future. Hadoop, MongoDB, Cassandra, InfluxDB – these were the new, exciting NoSQL databases. PostgreSQL was old and boring.

In 2017? I thought the NoSQL hype had subsided by then and everyone was excited about distributed transactions -- Spanner, Cockroach, Fauna, Foundation, etc.

politelemon 7 hours ago [-]
I think this just illustrates the tech bubble we live in. Occasionally we find one that doesn't match ours.
akulkarni 2 hours ago [-]
Exactly!

"The future is already here, it's just not very evenly distributed" - William Gibson

spooneybarger 2 hours ago [-]
Marketing is going to market.
dgellow 7 hours ago [-]
I had the same thought. They are off by a few years
Dowwie 3 hours ago [-]
My experiences with Timescale revealed the need for a full time DBA expert of TSDB to make the db viable for queries exceeding more than the last week of time series data. Tiered reads barely work at all. Do you want a degree in how to use a crippled Postgres offshoot?
sgarland 55 minutes ago [-]
Tbf, my experience as a DBRE has been that most places should have a DB expert on staff, especially for Postgres. I’ve not used TigerData / Timescale, but IME there’s far more complexity to reason about and manage than people think.
akulkarni 2 hours ago [-]
I'm sorry to hear about your experience. Would love to hear more if you are open to it: ajay [at] tigerdata [dot] com.
talos_ 9 hours ago [-]
IMHO, the bigger name conflict is with Tigris Data. Tigris means tiger and despite no tiger logo, they did have tiger stickers at events
aleksi 5 hours ago [-]
> Tigris means tiger

I'm pretty sure Tigris Data is named after the Tigris river (https://en.wikipedia.org/wiki/Tigris), and the name does not mean "tiger".

coldtea 4 hours ago [-]
You'd be surprised. Tigris is the latinized version of the name of the river in ancient Greek (τίγρης) which also means tiger in ancient Greek.

The common underlying etymology is an even older into-european term translated roughly as "sharp" or "pointy" (in the case of the tiger I guess referring to the teeth).

From a biblical etymology page:

The name Tigris shares its root with the word "tiger" (more precise: the word "tiger" and the name Tigris are identical in Greek). That means that in deep antiquity the tiger and the Tigris had signature qualities that were comparable and from which both derived their name. The word tiger and the identical name Tigris both come from the Avestan word tighri, which means arrow, or the more general tigra, which means sharp or pointed.

justinmitchel 19 hours ago [-]
> "Our cloud offering is “Tiger Cloud.” Our logo stays the same: the tiger, looking forward, focused and fast. Some things do not change. Our open source time-series PostgreSQL extension remains TimescaleDB. Our vector extension is still pgvectorscale."

Cool!

ejs 2 hours ago [-]
I've been using TimescaleDB for a while as a metrics datastore. It's really proven to be great for aggregating data without a lot of hassle (using continuous aggregates, retention policies, etc).

I recommend it when you don't want/need to have separate sources for account data and your metrics/aggregate data.

lukaslalinsky 10 hours ago [-]
At first I thought they were sold and the new owner didn't like the original name, but it doesn't seem to be the case. I don't really understand, why would somebody change a recognizable brand.
NewJazz 10 hours ago [-]
TimescaleDB will continue to be used to refer to the timeseries postgresql extension. One offering from what they consider to be a larger set of offerings.
jitl 10 hours ago [-]
Because they don’t want to be pigeonholed as “just time series things”. They continue selling a product called timescale, so I don’t think it’s a loss of brand in much measure.
coldtea 4 hours ago [-]
We only care for them to the degree they do "time series things".

Not for AI or other bs "pivots"

blitzar 6 hours ago [-]
pivot from time to ai
jamesgresql 5 hours ago [-]
Not the case!
ovaistariq 7 hours ago [-]
BTW there is another TigerData which predates this rename by a month: https://library.princeton.edu/about/library-news/2025/introd...
gagik_co 5 hours ago [-]
The original tiger bit could have originated from some of founders’ affiliations with Princeton too.
nelsonfigueroa 10 hours ago [-]
well at least they didn't append "AI" to their name
akulkarni 2 hours ago [-]
That was one of our requirements when we started discussing a name change. :-)
doctoboggan 10 hours ago [-]
> InfluxDB, and other NoSQL databases are seen as technical dead ends.

Is influxdb really seen as a dead end?

physicles 8 hours ago [-]
1.x and 2.x are, which is why 3.x reinvents the product around standard tech (true SQL, Apache Arrow). It's hard to ask customers to bet on a database when, to name one reason, its query language has already changed twice.
kawsper 9 minutes ago [-]
Every major release of InfluxDB have been a rewrite.

While 3. looks impressive, it seems like most of the interesting features are closed source, so not a 1:1 replacement for version 1.

InfluxDB Edge is open-source, but you need to depend on InfluxDB Community which is free, but closed source, to get things like include functionality like a compactor, which will add capabilities for deletes and re-organizing files to optimize for queries on longer time ranges.

They also need to resurrect all their old 1.* Client libraries for 3.*.

I love InfluxDB, but I’m not hopeful for its future.

akulkarni 2 hours ago [-]
No joke: We've had Influx customers come to us and say that migrating from Influx 1.x to Timescale was easier than migrating from 1.x to 2.x
lawn 7 hours ago [-]
I've been burned by influxdb abandoning their old versions one too many times and will never consider it for anything ever again.
suyash 1 hours ago [-]
Quite the opposite, InfluxDB 3 is the best time series database currently in the market in terms of features and performance.
blitzar 6 hours ago [-]
I use victoriametrics now, seems to be ok
dzonga 4 hours ago [-]
I met these folks one time in NYC, you could tell they were onto something big & bigger.
akulkarni 2 hours ago [-]
Thank you for recognizing that in us.
8K832d7tNmiQ 9 hours ago [-]
Why not TigerScale ?
totetsu 4 hours ago [-]
Sounds like a skin disease from Game of Thrones
nwhnwh 8 hours ago [-]
Tigers don't scale.
NewJazz 7 hours ago [-]
Tigers are great climbers.
bobosha 2 hours ago [-]
yet they do data.
aduwah 8 hours ago [-]
But you can scale a tiger
alexpadula 8 hours ago [-]
Literally last week I was looking at the logo and was like interesting they didn't go with a name using Tiger, Cheetah, etc. Cool name, though I must say Timescale was really cool name as well.
eska 4 hours ago [-]
Missed opportunity for the AI pivot: Taiger Data. I'll see myself out.
heeton 6 hours ago [-]
Bad choice imo, given that there is another database called tiger beetle. I assumed they’d merged when I saw the title.
pmalynin 10 hours ago [-]
Which has nothing to do with WiredTiger I guess?
georgewfraser 10 hours ago [-]
I talked to the timescale CTO at pg conf a few years ago and asked him what timescale does differently than a standard columnar database that makes it better suited for time oriented data. He said a bunch of things and I said “but columnar databases do those things.” Then he got mad at me.

I guess it’s just another columnar dbms after all?

dangoodmanUT 9 hours ago [-]
They don't do well on benchmarks https://benchmark.clickhouse.com/
akulkarni 2 hours ago [-]
It depends on which benchmarks you use.

"ClickBench evaluates databases using a single table of clickstream data, representative of workloads like web analytics, BI, and log aggregation. It also favors full-table large scans and large-scale aggregations on denormalized data.

Real-time analytics inside applications is different and needs a new benchmark." [0]

This is why we published RTABench. [1]

We believe that it is more representative of real-time analytical workloads.

[0] https://www.tigerdata.com/blog/benchmarking-databases-for-re...

[1] https://rtabench.com/

jascha_eng 2 hours ago [-]
I'd argue we do okay, but of course it's Clickhouses own benchmark it's hard to outperform them there. It's also not apples to apples. Clickhouse has much less transactional guarantees and isn't postgres SQL compatible. The great thing about Timescale is that you only need one DB for all your analytics and transactional needs. Combined with pgvector postgres also handles search quite well.

In a way Timescale is just postgres on steroids. Sure if you really know your use-case well, are fine with giving up some postgres nicenes, are willing to learn a new query language and are fine with using and syncing multiple data stores you'll outperform timescale. But I think it is still really cool to see how close you can get with essentially just a better postgres.

freilanzer 10 minutes ago [-]
DuckDB seems to be the most interesting there.
dengolius 4 hours ago [-]
Yes, TigerData aka Timescale tried to make a fuss a few years ago comparing Clickhouse and TimescaleDB, but they failed.
victorbjorklund 7 hours ago [-]
it does sound like a pretty dumb question. Many things do similar things. That is like asking what postgres does that other sql databases doesnt.
viccis 8 hours ago [-]
Do you think all time series databases (like InfluxDB for example) are useless compared to "columnar databases" that "do those things" or just Timescale?
yuretz 9 hours ago [-]
Few years have passed and your guess is still wrong.
fellatio 7 hours ago [-]
Unfair anecdote as you don't mention what he said before and after "he got mad" (whatever that means).
4 hours ago [-]
v5v3 6 hours ago [-]
"Why “Tiger”? The tiger has been our mascot since 2017, symbolizing the speed, power, and precision we strive for in our database. Over time, it’s become a core part of our culture: from weekly “Tiger Time” All Hands and monthly “State of the Tiger” business reviews, to welcoming new teammates as “tiger cubs” to the “jungle.”

Cringe...!!!

lijok 5 hours ago [-]
Can you imagine joining a company and getting referred to as a tiger cub. I suspect they don’t have much in way of HR
Freak_NL 4 hours ago [-]
It's all relative¹.

1: https://media.karousell.com/media/photos/products/2018/11/10...

coldtea 4 hours ago [-]
Companies with much in way of HR are even worse
coldtea 4 hours ago [-]
Yeah, the kind of BS a pointy-haired boss or tech-bro considers foster "company culture"
matsemann 3 hours ago [-]
Meh, it's just a bit of fun. While I don't lean too much into it myself, it's a good way of finding a company where all the grumpy hermits have self-selected themselves away.
freilanzer 6 minutes ago [-]
Not wanting to be a "tiger cub" introduced to the "jungle" does not make one a grumpy hermit.
2 hours ago [-]
4 hours ago [-]
eska 4 hours ago [-]
> “While I appreciate PostgreSQL every day, am I the only one who thinks this is a rather bad idea?” – top HackerNews comment on our launch (link)

I know it's popular to bash the HackerNews hivemind, and often it's honestly deserved, but this line is in bad taste. The comment was not only polite and professional, it was also right. They had to introduce a columnar storage format (hypertables) to make it work. That is exactly what the comment and the follow-up cocmment suggest.

4 hours ago [-]
rattray 10 hours ago [-]
Copying what I viewed as the key parts:

> The majority of workloads on our Cloud product aren’t time-series. Companies are running entire applications on us... So we are now “TigerData.” We offer the fastest PostgreSQL. ... Our cloud offering is “Tiger Cloud.” Our logo stays the same: the tiger, looking forward, focused and fast... Our open source time-series PostgreSQL extension remains TimescaleDB. Our vector extension is still pgvectorscale. Why “Tiger”? The tiger has been our mascot since 2017, symbolizing the speed, power, and precision we strive for in our database.

Given the logo (and internal company culture around the tiger mascot), I understand where they're coming from, but with the name conflicts (TigerBeetle, WiredTiger, etc) I do wish they'd chosen something else -- like maybe TiScaleDB and give a titanium sheen, do triple duty with the tiger and the Timescale heritage?

HackerThemAll 6 hours ago [-]
They did not have to choose anything else - timescaledb was just fine.
0xdeafbeef 7 hours ago [-]
There is already tidb :)
6 hours ago [-]
4 hours ago [-]
morelish 7 hours ago [-]
Choosing a name like that made me think they were acquired by TigerBeetle. Come on like
1 hours ago [-]
be87581d 9 hours ago [-]
[dead]
toddmorey 4 hours ago [-]
[flagged]
4 hours ago [-]
jamesgresql 19 hours ago [-]
Tiger here, let's go!
jeffchuber 10 hours ago [-]
going to be super confusing that there is now tigerdata and tigergraph - both database companies
jitl 10 hours ago [-]
also WiredTiger, the storage engine used by MongoDB https://github.com/wiredtiger/wiredtiger
Jarwain 10 hours ago [-]
Hey I mean I'm not super likely to use both tiger data and tiger graph, but using both tailscale and timescale has resulted in some awkward mixups
andyferris 10 hours ago [-]
Also tigerbeetle!
xeonmc 9 hours ago [-]
next: TigerSalamander