> 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.
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].
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.
In 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.
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.
Small 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.
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.
@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).
> 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.
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?
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.
Generally 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.
Readit News
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.
[0]: https://youtu.be/b2F-DItXtZs
There's an element of immaturity in the style that they should probably work on.
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.
* 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.
Also TigerBeetle is an insect, not a fast cat.
Fair. But a mascot is not a name. I hope you can see why I bring this up?
> Also TigerBeetle is an insect, not a fast cat.
It is? Damn. I thought a Tiger Beetle was a six foot long cat wearing costume wings and a springs for antennae?
Deleted Comment
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.
In 2017? I thought the NoSQL hype had subsided by then and everyone was excited about distributed transactions -- Spanner, Cockroach, Fauna, Foundation, etc.
"The future is already here, it's just not very evenly distributed" - William Gibson
Query optimization is one of those places where it can be easy to get orders of magnitude performance increases.