4 ms·

The deal-breaker for me with couchbase is that the community edition lags (in terms of bug fixes, security updates, etc) 8-10 months behind their commercially l

The deal-breaker for me with couchbase is that the community edition lags (in terms of bug fixes, security updates, etc) 8-10 months behind their commercially licensed offering.

arungupta 10y ago
Developers do have early access to the latest Couchbase EE versions for development and testing as long as they are not using it in production. If they are using Couchbase in production and they do not want to pay for EE, then they do have to live with the CE lags. This allows us to maintain a sustainable business model.
arungupta 10y ago
Some more points ... 1 - Unabashedly, our #1 commitment is to our customers who are relying on Couchbase for their mission critical applications. That's why the Couchbase Enterprise Edition gets the bulk of our attention and testing. 2 - History can show that's it's actually more like 3-6 months of delay rather that 8-10 and corresponds more to our release cycles than to an artificially imposed delay. 3 - Couchbase CE is provided as a service to the community. Users who want to rely upon their own expertise to run a database in production have a responsibility to themselves and their organization to have the appropriate level of skills to do so. That should mean being able to debug and fix bugs themselves. In fact, our open source code base does not lag AT ALL and anyone is welcome to build off of that themselves and get all of the latest and greatest features (and bugs of course). If they're not willing to do this, they should be paying us to.
arun_couch 10y ago
Arun from Couchbase, few points ... 1 - Unabashedly, our #1 commitment is to our customers who are relying on Couchbase for their mission critical applications. That's why the Couchbase Enterprise Edition gets the bulk of our attention and testing. 2 - History can show that's it's actually more like 3-6 months of delay rather that 8-10 and corresponds more to our release cycles than to an artificially imposed delay. 3 - Couchbase major releases has always had CE and EE in sync. 4 - Couchbase CE is provided as a service to the community. Users who want to rely upon their own expertise to run a database in production have a responsibility to themselves and their organization to have the appropriate level of skills to do so. That should mean being able to debug and fix bugs themselves. In fact, our open source code base does not lag AT ALL and anyone is welcome to build off of that themselves and get all of the latest and greatest features (and bugs of course). If they're not willing to do this, they should be paying us to.
- frankleng 10y ago
  3 is not quite true. tried deploying CE at scale at my last company, ran into a gnarly limit on concurrent connections the db cluster would handle. It was a hard coded, undocumented limit on the CE version. not sure if this still exists. but it took some digging into the source, and monkey patching to fix.
  - HodGreeley 10y ago
    Hod @ Couchbase here. EE would have had the same limits. If this is the limit I'm thinking of, it's there for a reason (defensive against malfunctioning implementations, and very rarely something that should be exceeded). It was increased at some point (not sure when). But CE is not crippled relative to EE.

The deal-breaker for me with couchbase is that the community edition lags (in terms of bug fixes, security updates, etc) 8-10 months behind their commercially licensed offering.

arungupta 10y ago

Developers do have early access to the latest Couchbase EE versions for development and testing as long as they are not using it in production. If they are using Couchbase in production and they do not want to pay for EE, then they do have to live with the CE lags. This allows us to maintain a sustainable business model.

arungupta 10y ago

Some more points ... 1 - Unabashedly, our #1 commitment is to our customers who are relying on Couchbase for their mission critical applications. That's why the Couchbase Enterprise Edition gets the bulk of our attention and testing. 2 - History can show that's it's actually more like 3-6 months of delay rather that 8-10 and corresponds more to our release cycles than to an artificially imposed delay. 3 - Couchbase CE is provided as a service to the community. Users who want to rely upon their own expertise to run a database in production have a responsibility to themselves and their organization to have the appropriate level of skills to do so. That should mean being able to debug and fix bugs themselves. In fact, our open source code base does not lag AT ALL and anyone is welcome to build off of that themselves and get all of the latest and greatest features (and bugs of course). If they're not willing to do this, they should be paying us to.

arun_couch 10y ago

Arun from Couchbase, few points ... 1 - Unabashedly, our #1 commitment is to our customers who are relying on Couchbase for their mission critical applications. That's why the Couchbase Enterprise Edition gets the bulk of our attention and testing. 2 - History can show that's it's actually more like 3-6 months of delay rather that 8-10 and corresponds more to our release cycles than to an artificially imposed delay. 3 - Couchbase major releases has always had CE and EE in sync. 4 - Couchbase CE is provided as a service to the community. Users who want to rely upon their own expertise to run a database in production have a responsibility to themselves and their organization to have the appropriate level of skills to do so. That should mean being able to debug and fix bugs themselves. In fact, our open source code base does not lag AT ALL and anyone is welcome to build off of that themselves and get all of the latest and greatest features (and bugs of course). If they're not willing to do this, they should be paying us to.

frankleng 10y ago
3 is not quite true. tried deploying CE at scale at my last company, ran into a gnarly limit on concurrent connections the db cluster would handle. It was a hard coded, undocumented limit on the CE version. not sure if this still exists. but it took some digging into the source, and monkey patching to fix.
- HodGreeley 10y ago
  Hod @ Couchbase here. EE would have had the same limits. If this is the limit I'm thinking of, it's there for a reason (defensive against malfunctioning implementations, and very rarely something that should be exceeded). It was increased at some point (not sure when). But CE is not crippled relative to EE.