31–40 of 220 posts
Can someone please summarize what it does because I couldn't figure out from website? It says its "on Postgres", is it a flavor of PG? or it sits on top of multiple PG instances.
If this is just postgresql, why would I use this implementation over postgresql? It also seems like it scales linearly with some decrease in ROI after 12 nodes.
It's not "just" PG, it's like a mega-extension with data-types and tuple-layout and a tonne of magic for the data-domain. You can, of course, make similar models with plain PG - in the same way one does GIS without PostGIS.
>All of these capabilities are being released under the Timescale License, our source-available license that permits broad usage, except for where organizations are providing TimescaleDB-as-a-service. So it's not open-source because AWS hasn't been nice with ElasticSearch and they don't want to be in the same situation?
That sounds like open source to me, I bet they're just being really conservative about saying "open source" because there's been so much backlash at MongoDB/Cockroach/etc for similar restrictions. It's restricted OSS because AWS takes things, runs them, and eats up all the potential revenue.
This is an interesting window into their business model. This could be a purely an altruistic decision, which businesses sometimes do, contrary to popular belief. More likely it's a bet that wider adoption from making the clustered version free will drive more revenue through their managed database as a service offering. Which shows that their non-OSI open-source license is actually leading to more code and features…
(Timescale CEO and post author) You are spot on. Before the Timescale License, we were left with a tough decision: do we open-source a feature so that everyone can have it for free OR do we close a feature so that the mega-clouds don't have access to it? We didn't like either of those options, which is why we created the Timescale License, which allows us to offer capabilities for free (and make the source code avail…
This is an interesting window into their business model. This could be a purely an altruistic decision, which businesses sometimes do, contrary to popular belief. More likely it's a bet that wider adoption from making the clustered version free will drive more revenue through their managed database as a service offering. Which shows that their non-OSI open-source license is actually leading to more code and features…
Earlier quoted context omitted.
That sounds like open source to me, I bet they're just being really conservative about saying "open source" because there's been so much backlash at MongoDB/Cockroach/etc for similar restrictions. It's restricted OSS because AWS takes things, runs them, and eats up all the potential revenue.
> That sounds like open source to me, I bet they're just being really conservative about saying "open source" because people there's been so much backlash at MongoDB/Cockroach/etc for similar restrictions. Open Source has a very defined meaning. Please read up on the history of open source and source available licenses before saying it is all the same. We've been defending it against a number of attacks and we will p…
Throw in an expiry date, dual licensing (pay to play seems more than fair) and I'm content. History be damned.
I'm so sick of it. Just because one group defines it a certain way doesn't make it gospel. The OSI has no power over me.
Edit: wording
This is an interesting window into their business model. This could be a purely an altruistic decision, which businesses sometimes do, contrary to popular belief. More likely it's a bet that wider adoption from making the clustered version free will drive more revenue through their managed database as a service offering. Which shows that their non-OSI open-source license is actually leading to more code and features…
(Timescale CEO and post author) You are spot on. Before the Timescale License, we were left with a tough decision: do we open-source a feature so that everyone can have it for free OR do we close a feature so that the mega-clouds don't have access to it? We didn't like either of those options, which is why we created the Timescale License, which allows us to offer capabilities for free (and make the source code avail…
That said I find it's fairly tedious to do a lot of time-series analysis and pattern discovery/anomaly detction across rich event models (think aws cloudtrail events).
Anything TimescaleDB can help with here? Are there case studies you can point us to? It feels like there is probably home for both just in my domain and quite obviously in the broader context of large enterprise ops/security.