Multi-node TimescaleDB is now free
blog.timescale.com
Multi-node TimescaleDB is now free
1–10 of 220 posts
Re: Multi-node TimescaleDB is now free
#2>67k line PR
Man I'm glad I don't have to review that
Re: Multi-node TimescaleDB is now free
#3Hi, I authored this post, but the credit really goes to the Timescale database team.
Multi-node TimescaleDB is the result of a massive amount of engineering effort over two years, as can be seen in this +67,000 line PR: https://github.com/timescale/timescaledb/pull/1923
We're thrilled to make this free so that more developers can use it.
Re: Multi-node TimescaleDB is now free
#4This 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 being available free and (mostly) open-source. As opposed to gating features for paying customers.
I think we're too hung up on OSI open source licenses. The additional restriction in the timescaledb license that you can't run a paid database as a service offering affects hardly anyone negatively (AWS). It affects us all positively by providing a sustainable business model to support additional development and support of an open-source product we use. Win-win if ever there was one. I'd like to see more open-source and closed-source companies consider this model.
Re: Multi-node TimescaleDB is now free
#5>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?
Re: Multi-node TimescaleDB is now free
#6Hi, I authored this post, but the credit really goes to the Timescale database team. Multi-node TimescaleDB is the result of a massive amount of engineering effort over two years, as can be seen in this +67,000 line PR: https://github.com/timescale/timescaledb/pull/1923 We're thrilled to make this free so that more developers can use it.
I'm not sure a 67k line PR proves anything more than 'noone really reviewed this'.
Re: Multi-node TimescaleDB is now free
#7>67k line PR Man I'm glad I don't have to review that
To be clear, it was developed in a branch so all the individual commits have been reviewed beforehand when landing on that branch. And the branch was rebased throughout the development cycle. This is just the final PR to merge that branch back into master :)
Re: Multi-node TimescaleDB is now free
#8A few days ago I went to your site to check if the distributed stuff had arrived, good to see it's here! You're making incredible software.
Re: Multi-node TimescaleDB is now free
#9Hi, I authored this post, but the credit really goes to the Timescale database team. Multi-node TimescaleDB is the result of a massive amount of engineering effort over two years, as can be seen in this +67,000 line PR: https://github.com/timescale/timescaledb/pull/1923 We're thrilled to make this free so that more developers can use it.
I'm not sure a 67k line PR proves anything more than 'noone really reviewed this'.
Or that there was a huge development effort going in a private branch that had PRs and code review for each of the 226 commits :)
Re: Multi-node TimescaleDB is now free
#10>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.