🐈
zeeSQL
  • zeeSQL, SQL and search by value for Redis. Fast, Simple and Reliable.
  • How to
    • How to choose between QUERY and EXEC
    • know-what-secondary-indexes-are defined
    • How to load zeeSQL in Redis
    • How to check if an index is used in zeeSQL and SQLite
    • know-what-secondary-indexes-are defined
    • create-an-index
    • create-a-view
    • create-a-secondary-index
    • How to create a trigger
    • quickly-ingest-data
    • How to copy a database
    • get-help
    • work-with-dates
    • using-full-text-search
    • work-with-json
    • How to create a new database in zeeSQL
    • How to create a new table in zeeSQL
    • know-what-tables-are-defined
    • know-what-databases-are-defined
    • works-with-boolean
    • How to get zeeSQL
    • How to get JSON output
    • add-multiple-rows
  • blog
    • node
      • Using RediSQL with Node.js
    • JSON on Redis via RediSQL, SQL steroids for Redis
    • golang
      • Using RediSQL with Go(lang)
    • Doubling the performances of RediSQL, SQL steroids for Redis.
    • zeeSQL now runs on SQLite 3.35
    • Query Redis on two attributes
    • RediSQL for analytics
    • Copying RediSQL databases
    • Release 0.9.0 of RediSQL, SQL steroids for Redis
    • Release 0.8.0 of RediSQL, SQL steroids for Redis
    • Release 0.7.0 of RediSQL, SQL steroids for Redis
    • JSON on Redis via RediSQL, SQL steroids for Redis
    • Release 0.6.0 of RediSQL, SQL steroids for Redis
    • python
      • using-redisql-with-python
    • Release 0.5.0 of RediSQL, SQL steroids for Redis
  • References
  • zeeSQL commits to backward compatibility
  • zeeSQL, a solid product for busy developer
  • zeeSQL and secondary indexes, how to search Redis key by value
  • Tutorial
  • Pricing for zeeSQL
  • Why you should migrate from RediSQL to zeeSQL
  • FAQs
  • Motivation
Powered by GitBook
On this page
  • Advatanges
  • Disadvantages

Was this helpful?

zeeSQL, a solid product for busy developer

zeeSQL is not an open source project. I tried really hard to make RediSQL sustainable while being completely open source. Unfortunately I failed.

The product was stolen and used against its own license.

Between the choice of abbandoning the project and monetize it in a not open-source way, I decided to try to monetize it.

Advatanges

Being a closed source project, tht people pay real money for it, comes with a series of advantages.

Having the main developer of the project keep working on it, enhancing, and writing documentation for it, is invaluable. It is much more likely that the documentation will be of high quality. There is a clear incentive in having a well documented and easy to use project.

(This is not always the case for projects that sell supports, nor it is always the case for project that sell computing resources.)

Also, the possibilities that the project get abbandoned in the foreseable futures are extremely slim. It is a source of income for the author who has all the incentives to keep expading it.

Disadvantages

The main disadvanates of having the source code of the project not open, is that it is impossible to modify the source code yourself.

During the years of work with RediSQL, very few people tryied to submit valuable Pull Request, and I don't really think that this would change with zeeSQL.

Another disadvantage of a closed source project is that it won't be possible for your organization to run the project indipendently.

This is not a problem, as long as RedBeardLab is around and keep working on zeeSQL, but it could be a real problem in the next 5 or 10 years.

To avoid this problem, we pledge to release the source code of zeeSQL as soon as we are unable to support it anymore.

PreviouszeeSQL commits to backward compatibilityNextzeeSQL and secondary indexes, how to search Redis key by value

Last updated 4 years ago

Was this helpful?