3 ms·
I recently did some 'lock-in' consulting with a company who had heavily committed to an open source database. The database had two versions, community and enter
by Railsify 7y ago
I recently did some 'lock-in' consulting with a company who had heavily committed to an open source database. The database had two versions, community and enterprise, previously both were open source with the enterprise version optionally being supported by a service contract. The company then changed the license of the enterprise version to a closed source pay only subscription model with a HUGE yearly license fee. The tech team are now eating major crow from the business side of the company. I ultimately recommended that they rewrite the data access layer to use PostgreSQL. Which they are doing, in the end it will result in a more modular and extensible application architecture. Lock-In is something that should be avoided.
- omgpennies 7y agoWas this by any chance Cassandra? Sounds an awful lot like what Datastax did a couple years ago.
- Railsify 7y agoI don't want to be too explicit but there are several cases of this in the past few years. The playbook was the same as Cassandra. Open source as a marketing tool...
- deogeo 7y agoCould they not still use the last open enterprise version? At least until they can migrate. Which is troublesome, but at least buys you time - something you wouldn't have if the database never had a free/open-source version.
- Railsify 7y agoYes, that is exactly what is happening.