[HN Gopher] Citus: Make enterprise features open source
       ___________________________________________________________________
        
       Citus: Make enterprise features open source
        
       Author : ahachete
       Score  : 58 points
       Date   : 2022-06-16 20:07 UTC (2 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | endisneigh wrote:
       | Is it possible to easily configure Postgres/Citus such that you
       | can replicate your database across a managed offering such that
       | if your database load is sufficiently high then you start using
       | the managed offering, otherwise you use your managed offering?
       | 
       | Being able to combine the cheap compute of something like Hetzner
       | with the high availability of a managed offering would be nice.
        
         | mslot wrote:
         | Not right now. It's definitely something that's on our radar,
         | but it'll take a while to get there.
        
       | JelteF wrote:
       | Really nice seeing this commit, that I pushed this morning to
       | Github, on the frontpage of HN a few hours later :) It's awesome
       | that other people are just as excited about open-sourcing as we
       | are. But if you like this definitely keep an eye on our blog[1]
       | and/or twitter[2] for the upcoming "official" announcements. They
       | will have a lot more info on this and all the other cool changes
       | things that are part of Citus 11.
       | 
       | [1]: https://www.citusdata.com/blog/
       | 
       | [2]: https://twitter.com/citusdata
        
       | whitepoplar wrote:
       | This is fantastic, and should bring some relief to those who want
       | to self-host Citus outside of Azure. I wonder if TimescaleDB's
       | recent license changes had anything to do with this.
        
         | Tostino wrote:
         | Wasn't aware of this change until I saw you mention it:
         | https://docs.timescale.com/timescaledb/latest/timescaledb-ed...
        
         | mfreed wrote:
         | I'm not sure what "recent license changes" you are referring
         | to?
         | 
         | The Timescale License was introduced in late 2018, although we
         | never _relicensed_ any of our Apache 2 code, we only created a
         | space for _new_ capabilities to be developed under these terms.
         | 
         | There were a few changes to the license in Sept 2020, but those
         | only liberalized a few clauses (including from feedback we
         | received from the Hacker News community, including the "right
         | to repair" and "right to improve"). At the time, we also moved
         | any remaining "enterprise" features from an Enterprise/Paid
         | license into the TSL/Community/Free license.
         | 
         | https://www.timescale.com/blog/building-open-source-business...
         | 
         | We haven't changed anything since, nor have we ever moved any
         | Apache-2 code into the TSL.
         | 
         | (Timescale cofounder)
        
           | whitepoplar wrote:
           | Time really flies by! I was referring to you guys moving all
           | enterprise features into the TSL/Community license.
        
       ___________________________________________________________________
       (page generated 2022-06-16 23:00 UTC)