15 ms·
Timescale Is Now TigerData
- justinmitchel 1y 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!
- jamesgresql 1y agoTiger here, let's go!
- jeffchuber 1y agogoing to be super confusing that there is now tigerdata and tigergraph - both database companies
- andyferris 1y agoAlso tigerbeetle!
- xeonmc 1y agonext: TigerSalamander
- jeffchuber 1y agohow could i forget!
- jitl 1y agoalso WiredTiger, the storage engine used by MongoDB https://github.com/wiredtiger/wiredtiger https://github.com/wiredtiger/wiredtiger
- jeffchuber 1y agoof course!
- Jarwain 1y agoHey 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
- apgwoz 1y agoSo there’s TigerData and TigerBeetle. I wish they would have chosen a different fast cat…
- pcthrowaway 1y agoAlso WiredTiger https://en.wikipedia.org/wiki/WiredTiger https://en.wikipedia.org/wiki/WiredTiger
- kajecounterhack 1y agoI know what you mean, but still Tiger Beetles are an insect https://en.wikipedia.org/wiki/Tiger_beetle https://en.wikipedia.org/wiki/Tiger_beetle
- apgwoz 1y agoI 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.
- sidewndr46 1y agoNow they just need to rebrand as Tiger Direct!
- deleted 1y ago[deleted]
- alexpadula 1y agoWildcatDB, 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.
- evanelias 1y agoSmall corrections: RocksDB's logo is a cheetah. MariaDB's is a sea lion, which is similar to a seal, but is delightfully relevant to this thread due to sounding more cat-like.
- pmalynin 1y agoWhich has nothing to do with WiredTiger I guess?
- nelsonfigueroa 1y agowell at least they didn't append "AI" to their name
- akulkarni 1y agoThat was one of our requirements when we started discussing a name change. :-)
- 28304283409234 1y agoMissed opportunity for TaigerData ;-)
- akulkarni 1y ago:-) I can't imagine the comments if we had chosen that...
- doctoboggan 1y ago> InfluxDB, and other NoSQL databases are seen as technical dead ends. Is influxdb really seen as a dead end?
- physicles 1y ago1.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.
- lawn 1y agoI've been burned by influxdb abandoning their old versions one too many times and will never consider it for anything ever again.
- akulkarni 1y agoNo 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
- kawsper 1y agoEvery 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.
- pauldix 1y agoInfluxDB Founder & CTO here. We worked hard to support InfluxQL in 3.x and it supports the v1 write API. Admittedly, it will be a migration to move and we haven't yet built the tooling, but we felt it was important to get the 3.0 release out even though we don't have the migration tooling built yet. Our plan is to have that available later this year. The 2.x to 3.x move is, admittedly, much harder. This is because of the language Flux. We haven't been able to bring that over to 3.x in a way that makes it useful. We actually built a bridge for it in our cloud offering, but our experience is that the performance isn't good enough to be acceptable for customers wanting to upgrade. If they want to make the move, adopting SQL or InfluxQL is likely the only path. We'll continue to develop 3.x and we'll build more migration tooling over time. I think we can build specialized tooling to help Flux users migrate over to 3.x with query translation tools, but there are more features we need to land in 3.x to enable that first. We're committed to the technology stack (Apache Arrow & DataFusion) and the 3.x line. We have no plans for another major release. I'll be happy if we end up releasing 3.56.2 8 years from now.
- ethagnawl 1y agoThis 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.
- lukaslalinsky 1y agoAt 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 1y agoTimescaleDB 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 1y agoBecause 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 1y agoWe only care for them to the degree they do "time series things". Not for AI or other bs "pivots"
- blitzar 1y agopivot from time to ai
- jamesgresql 1y agoNot the case!
- gangstead 1y agoThen why reference the "Agentic Era" in the title?
- georgewfraser 1y agoI 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?
- yuretz 1y agoFew years have passed and your guess is still wrong.
- dangoodmanUT 1y agoThey don't do well on benchmarks https://benchmark.clickhouse.com/ https://benchmark.clickhouse.com/
- dengolius 1y agoYes, TigerData aka Timescale tried to make a fuss a few years ago comparing Clickhouse and TimescaleDB, but they failed.
- jascha_eng 1y agoI'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.
- hodgesrm 1y ago> Clickhouse has much less transactional guarantees ... Is this relevant? The benchmark is just reads.
- rattray 1y agoCopying 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?
- 0xdeafbeef 1y agoThere is already tidb :)
- deleted 1y ago[deleted]
- HackerThemAll 1y agoThey did not have to choose anything else - timescaledb was just fine.
- deleted 1y ago[deleted]
- 8K832d7tNmiQ 1y agoWhy not TigerScale ?
- be87581d 1y ago[dead]
- talos_ 1y agoIMHO, the bigger name conflict is with Tigris Data. Tigris means tiger and despite no tiger logo, they did have tiger stickers at events
- aleksi 1y ago> Tigris means tiger I'm pretty sure Tigris Data is named after the Tigris river (https://en.wikipedia.org/wiki/Tigris https://en.wikipedia.org/wiki/Tigris), and the name does not mean "tiger".
- coldtea 1y agoYou'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.
- talos_ 1y agoIn French, the river and the animal are both "tigre"
- alexpadula 1y agoLiterally 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.
- cakoose 1y 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 1y agoI think this just illustrates the tech bubble we live in. Occasionally we find one that doesn't match ours.
- akulkarni 1y agoExactly! "The future is already here, it's just not very evenly distributed" - William Gibson
- dgellow 1y agoI had the same thought. They are off by a few years
- spooneybarger 1y agoMarketing is going to market.
- smokel 1y 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.
- baggiponte 1y agoYeah they might be good but the marketing is really bold and, to a certain extent, arrogant if not outright disgusting.
- suyash 1y agoIt 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.
- mellosouls 1y agoAlso 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 1y agoI concur, the tone is very off-putting.
- sgarland 1y agoCassandra 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 https://youtu.be/b2F-DItXtZs
- jabiko 1y agoWe'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 1y 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).
- morelish 1y agoChoosing a name like that made me think they were acquired by TigerBeetle. Come on like
- deleted 1y ago[deleted]
- conradev 1y agoTigerData 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 https://github.com/tigerbeetle/tigerbeetle
- igitur 1y agoWhen I saw the headline I immediately thought that TigerData is somehow related to the TigerBeetle.
- ovaistariq 1y agoBTW there is another TigerData which predates this rename by a month: https://library.princeton.edu/about/library-news/2025/introducing-tigerdata-comprehensive-data-management-service-princeton https://library.princeton.edu/about/library-news/2025/introd...
- gagik_co 1y agoThe original tiger bit could have originated from some of founders’ affiliations with Princeton too.
- rbaudibert 1y agoTIL you can have GIFs as the `og:image` and Slack and friends will render them as GIFs, actually wild
- v5v3 1y 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 1y agoCan you imagine joining a company and getting referred to as a tiger cub. I suspect they don’t have much in way of HR
- coldtea 1y agoYeah, the kind of BS a pointy-haired boss or tech-bro considers foster "company culture"
- matsemann 1y agoMeh, 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 1y agoNot wanting to be a "tiger cub" introduced to the "jungle" does not make one a grumpy hermit.
- heeton 1y agoBad choice imo, given that there is another database called tiger beetle. I assumed they’d merged when I saw the title.
- toddmorey 1y ago[flagged]
- deleted 1y ago[deleted]
- dzonga 1y agoI met these folks one time in NYC, you could tell they were onto something big & bigger.
- akulkarni 1y agoThank you for recognizing that in us.
- eska 1y 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.
- deleted 1y ago[deleted]
- akulkarni 1y agoThat's fair. We referenced that quote because it captured a lot of the skepticism in the early days (and because that comment is public). No hard feelings though!
- eska 1y agoThat’s fair, but I would never point out a single individual over this, even if they were really mean about it. It’s just not a good look. Together with the other paragraph with the bashing of the competition this just looks like your company starts to develop an echo chamber where you’re internally so fine with speaking like that, that it leaks out to the public. For comparison, at my company we don’t even speak about our competition like that internally. Let your readers come to the conclusion that you’re better than the competition by showing the necessary facts only.
- eska 1y agoMissed opportunity for the AI pivot: Taiger Data. I'll see myself out.
- zlib 1y agoTimescale is much better
- koakuma-chan 1y agoThey should have kept timescale
- halfmatthalfcat 1y agoAge as old as time. My favorite on is Typesafe -> Lightbend -> Akka, and by favorite, most annoying.
- gregors 1y agoTimescale is sooooo much better. What a bad decision.
- Dowwie 1y agoMy 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?
- akulkarni 1y agoI'm sorry to hear about your experience. Would love to hear more if you are open to it: ajay [at] tigerdata [dot] com.
- sgarland 1y agoTbf, 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.
- pixl97 1y agoGenerally developers need to be watched so they don't blow up the application performance and so they reuse queries in the correct manner so you optimize things like the query cache and the indexes you have. Query optimization is one of those places where it can be easy to get orders of magnitude performance increases.
- sgarland 1y agoAgreed, though it’s also a monstrous effort to get devs to stop chucking everything into JSON, or my new favorite hell, serializing entire classes and storing them as a BLOB. It’s my fervent belief that we should revert to specialized roles, with a DB team designing schema and queries based on a team’s needs, who can access them via API only. Slows down velocity? Yes. Faster queries and more efficient use of resources? Yes. Fewer incidents and better referential integrity? Also yes.
- orphea 1y agoSlightly 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.
- ejs 1y agoSince this is a timescaleDB topic, would timescale not work? (With a basic DB and a few continuous aggregates running in the background?)
- skowalak 1y agoAt 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 1y agoI would go with InfluxDB, actually it's powers several Home Assistant apps behind the scene already for a reason.
- suyash 1y agobtw I work at InfluxData and happy to answer any question, just ask here or reach our in our forums
- Rebelgecko 1y agoIf 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 1y agoI'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.
- deleted 1y ago[deleted]
- victorbjorklund 1y agoIn a way I guess this makes sense because they are not just doing time series anymore but on the other hand that is just a very strange name. I'm just thinking about Tiger Beetle and I'm sure they will lose so much in brand awareness because people have heard about timescale db but they have not heard about tiger data and the name just sounds so cheesy.
- tianqi 1y agoWhenever I see a news headline mentioning that one of my critical dependencies is undergoing changes that make no technical sense, I get real fear. I feel like Jon Snow facing the army, as if I can see a tidal wave of devops work and code fixes coming my way. I really hope that these infrastructure product teams can be considering and not change something that is working well just for the sake of it. Even if they did a really smooth job, that sense of fear itself is a hurt to the brand - making me feel that this product is a source of fear.
- geodel 1y agoSo we do have Tiger management, Tiger base, Tiger Systems. Now with Tiger data if they all combine we may have a TigerDBMS.
- ahmadtbk 1y agoTimescale is a much cooler name. Also heres a conversation I just had with Jippity. There are some nicer names imo. https://chatgpt.com/share/6852de93-1384-8004-ac63-4ae93a8373c0 https://chatgpt.com/share/6852de93-1384-8004-ac63-4ae93a8373...
- richajak 1y agoMost probably their new name TigerData is influenced by their lead investor during Series C funding, Tiger Global Management. It is just my guess.