rediSQL

Hi Folks, I am developing RediSQL (https://www.redisql.com) a project that has an open and a closed source "PRO" part. The open source part is accessible on github (https://github.com/RedBeardLab/rediSQL) while the closed source one is not accessible and I just sell the binary. For several reason I would like to change the business strategy. The new strategy will include push all the features on the free version and enable telemetric, while the PRO version would simply not have the telemetric active. User of the free version can use all the features, but they need to constantly contact my servers, while user of the PRO version don't need to contact my servers at all. If the telemetric is active (free version) and it fails for some reason, the software simply shut down. The difference between the PRO version and the free version, hence wi

When I get started to build RediSLQ I wanted an interprocess, fast, data store that supported SQL manipulation. It may be useful to you as well: RediSLQ.com Or on GitHub: https://github.com/RedBeardLab/rediSQL Full disclaimer: I am the author

You could have a look into RediSLQ (RediSLQ.com) which is a redis module that embed SQLite, giving crazy fast performance. It gives you a lot of interesting concepts like "lightweight databases" or push queries result into streams. Here the GitHub repo: https://github.com/RedBeardLab/rediSQL Full disclaimer, I am the author.

Once I was building a small application, I didn't want to use a whole database such as postgres that is amazing but does require some maintenance, so I settled for using just Redis. It was fine but the lack of constrains and structure was killing me making everything harder, but I liked the zero maintenance things... So I build RediSQL[1] a module to provide SQL capabilities to Redis to get the best of both worlds: stability, easy maintenance, velocity, constrains and structure in data. [1]: https://github.com/RedBeardLab/rediSQL

I am in the process of doing something similar with rediSQL [https://github.com/RedBeardLab/rediSQL]. I would love any further feedback you can share.

I love SQL and I believe it will have a big jump in popularity with microservices. Each service should have a separate data source and being the sole responsable of a specific part of the data. In this environment however a full RDBMS is a little an overkill. The solution I am working on is RediSQL: https://github.com/RedBeardLab/rediSQL It is a Redis module that embed SQLite. Redis is nowadays a common piece in any infrastructure. The little module plugs into Redis and expose a new command REDISQL.EXEC that provide the ability to run SQL statement. It is multithread, does not impact the performance of Redis, and very simple to use. Great write performance, I got 50k inserts per second on my machine, that should be enough for most microservices. I would love any kind of feedback on the module or if you need any help to get you started jus

Quite related, but if you want to use Redis as a SQL database I wrote an extension to do just that: https://github.com/RedBeardLab/rediSQL It is a relative thin layer of rust code between the Redis module interface and SQLite. At the moment you can simply execute statements but any suggestion and feature request is very welcome. Yes, it is possible to do join, to use the LIKE operator and pretty much everything that SQLite gives you. It is a multi-thread module, which means that it does NOT block the main redis thread and perform quite well. On my machine I achieved 50.000 inserts per seconds for the in memory database. If you have any question feel free to ask here or to open issues and pull request in the main repo. :)

I am following two projects one extremely technical and another more sale oriented. The technical one is rediSQL[1] I am embedding SQLite into a redis module. Until few days ago I had performance issues that I wasn't able to figure out and I tracked everything in an issues. I finally figured out the problem, solve it, gain a lot of performance and I am about to write a blog post about. The next step is to get the exact same performance in the redis module compared with using SQLite embedded in a simple C program it is not going to be easy and I would probably defer this performance gain opportunity in favor of more features in the module. The second project, the sale oriented one, is WalOfStickers.com[2] where I try to sell hexagonal stickers for laptop. I like to show the technology that I work with and make my laptop mine, but I don't l