Hey! Maybe mfreed could answer this but how does this affect users of Timescale as part of Azure's Managed Posgres service, is this something that will still continue to be available?
Azure Postgres offers the Apache-2 Edition of TimescaleDB, not the Community Edition (which the TSL applies to). Same with DigitalOcean, Rackspace, Scaleways, Alibaba, etc.
So they can continue to offer the Apache-2 Edition, but could not before, and still can't, offer the Community Edition.
Community is where a lot of our more advanced features lie: multi-node, columnar compression, continuous and real-time aggregates, automation, advanced analytics, etc.
fwiw, I've spent 10 minutes scouring the timescale.com but I can't find any information about the difference between the Apache-2 Edition or the Community edition. Links from your GitHub readme suggest that such information used to be there, but now it's all "cloud" vs "software" - if I choose "software", which of the two editions do I get?
I assume this is still a WIP since the recent licensing / business model changes likely also warranted website changes, hence my feedback.
Congrats on the move btw, and fantastic that Timescale Cloud is working so well as a business model. Are you considering adding other clouds? I ask for selfish reasons as we're currently on Digital Ocean and quite happily so. If Timescale Cloud would exist for DO we'd likely become a customer.
In fact, if your business model succeeds and gets adopted by other open source vendors, supporting a wide range of clouds and hosting providers might very well help directly undermine the current effective oligopoly that is AWS/GCP/Azure! That'd be just splendid. Sorry for rambling a bit :-)
The "Software" column of product page [0], which I assume you are referring to, corresponds to our Community Edition, as least from a feature-set edition.
But thanks for the feedback. Always a balance between making things easily understandable and too much "in the weeds." We used to separately show "Community" and "Apache-2" on our feature matrix on product page, but frankly, it was too confusing / too much information for visitors that were just coming to TimescaleDB for the first time. Especially given that the vast, vast majority of deployments are indeed the Community edition.
For a detailed comparison, our docs should explicitly label all community features as "Community Edition". Otherwise, they are Apache-2. For example, see the labelling with compression [1], continuous aggregates [2], etc.
And we continue to provide binary packages for the Apache-2 edition of the TimescaleDB, which you can similarly find through our installation instructions (eg [3]).
It is Apache version of TimescaleDB there (right?), which stays the same. While, those, who are using TimescaleDB under Timescale license, e.g., on premise, have now right to repair, for example.
So they can continue to offer the Apache-2 Edition, but could not before, and still can't, offer the Community Edition.
Community is where a lot of our more advanced features lie: multi-node, columnar compression, continuous and real-time aggregates, automation, advanced analytics, etc.