update readme and doc for next release

Author: siscia

README.md

@@ -71,7 +71,7 @@ You will be able to manage and search for data.
 
 RediSQL is a Redis module, hence you will need a modern version of [Redis (> 5.0)][redis-download] and the RediSQL .so file.
 
-You can obtain RediSQL directly [from our store.](https://payhip.com/RediSQL)
+You can obtain RediSQL directly [from our store.][store]
 
 Alternative you can download the module from [github release.](https://github.com/RedBeardLab/rediSQL/releases)
 
@@ -89,6 +89,8 @@ All the commands are documented in [the references.][api]
 
 To explore RediSQL you can use the official client `redis-cli` which it will connect to the running server.
 
+The free version requires connection to our servers, make sure to set up your firewall appropriately.
+
 ## Docker image
 
 Moreover, also a Docker image is provide. Is sufficient to run the image `siscia/redisql` to start the Redis server with RediSQL loaded.
@@ -161,6 +163,27 @@ OK
    4) "ccc"
 127.0.0.1:6379> 
 ```
+
+## Telemetrics and commercial product
+
+From version 1.0.0 we move away from an open-core model where some features where not released as open source to a different model that force not-paying user to send telemetrics data to our servers.
+This allow us to release all the features of RediSQL as open source while retaining our possibilities to fund the project.
+[The full announcement on our blog][release-1.0.0].
+
+Of course the telemetrics data are not sensible (it is the result of the `REDISQL.STATISTICS` command) and we took all the precaution to allow smooth operation of the telementrics, [more details in the technical blog post.][redisql-telemetrics]
+
+The main idea behind forced telemetrics is that small users won’t be bothered by them too much. Moreover they usually have the resource, knowledge and will to set up their own firewall and invest time instead of money.
+
+All the other users can instead use the PRO version, the PRO version does not requires any connectivity to our servers, all the telemetrics part is simply not compiled into the code.
+
+We hope to have strike a good balance with this new policy.
+
+For a company is a bargain to just paid to don’t have one more thing to keep track of.
+
+For small users we allow them to use all the PRO features of RediSQL while just requiring a little more time and attention, of course small users can purchase the PRO version as well.
+
+The PRO version -- no telemetrics required -- version of RediSQL [can be purchased on our store][store].
+
 ## Documentation
 
 The complete API are explained in the official documentation that you can access here: [API References][api]
@@ -169,12 +192,19 @@ The complete API are explained in the official documentation that you can access
 
 I am going to accept pull request here on github.
 
-## License
+## License and commercial product
+
+This software is released under a custom license inspired by the MIT License.
+
+The "RediSQL License" add one clause to the MIT license that simply requires that you leave the telemetrics alone.
 
-This software is licensed under the AGPL-v3, it is possible to purchase more permissive licenses.
+It is possible to purchase more permissive licenses.
 
 <RediSQL, SQL steroids for Redis.>
 Copyright (C) 2019  Simone Mosciatti
 
+[store]: https://payhip.com/RediSQL
 [api]: http://redisql.redbeardlab.com/rediSQL/references/
 [redis-download]: https://redis.io/download
+[release-1.0.0]: http://redbeardlab.com/2019/04/09/redisql-release-1-0-0-change-in-strategy-and-business-model/
+[redisql-telemetrics]: http://redbeardlab.com/2019/04/09/telemetrics-for-redisql/

doc/docs/pro.md

@@ -4,74 +4,22 @@ This document explains the architecture and principle of working of RediSQL PRO.
 
 You can purchase RediSQL PRO, along with support [**here.**][signup]
 
-Motivation and details about the cost are [described here][pro_motivations].
-
 ## Main difference
 
-The PRO version offers two main features: **non blocking command** and **replication**
-
-### Non-blocking command
-
-Most command in RediSQL, all but `REDISQL.CREATE_DB`, are blocking command.
-
-This means that Redis block the client, pass the command to a background thread that actually executed it and finally the result is returned to client unblocking it.
-
-This works great in most cases, the main thread of Redis is free of doing other work (like answering standard redis command), there is no difference from the client point of view and your machine can use more than the single thread of redis to work for you.
-
-However, sometimes you want to have non-blocking commands.
-
-The blocking command will be executed in the main redis thread, this means that no other works will be done by Redis while executing your command.
-
-We could expect the non-blocking command to be slightly faster (smaller latency) than the blocking one since there is no need for coordination between threads.
-
-Finally, non-blocking commands are necessary for replication.
-
-Non-blocking commands are invoke adding the `.NOW` suffix.
-
-As an example, instead of `REDISQL.EXEC` that is a blocking command you can use `REDISQL.EXEC.NOW` to use the non-blocking version.
-
-#### When to use non-blocking commands
-
-Non-blocking command takes the priority over blocking one.
-
-Said so, generally, we are expecting users to use mostly the blocking commands.
-
-However, if you need a very quick insert or a very quick lookup, then you should use the non-blocking version.
-
-It is a bad idea to use non blocking commands for slow statements/query.
-
-This because while you are executing a non-blocking command the main redis thread cannot do anything else, this means it cannot answer other redis commands.
-
-### Replication
-
-Redis offers two main methods for persisting data on disk so that in case of power failure of disastrous failure your data are reasonably safe.
-
-RediSQL implement RDB persistency on the community version and AOF replication on the PRO version.
-
-For the details of this two method, I suggest to read the Redis Documentation [on this page][redis_persistence].
-
-The mechanism behind AOF replication is exactly the same behind cluster replication used by redis. The same **bytes** used for AOF replication are also used for cluster replication, just send over different sockets.
-
-For details about cluster replication you can consult the official Redis Documentation on [cluster][redis_cluster] and on [replication][redis_replication]
-
-The PRO version, indeed, implements both AOF and cluster replication.
-
-#### Effective use of Replication
-
-In order to use replication effectively, you should understand a few simple concepts.
-
-If a command is replicated it means that it could be re-executed.
-
-It is **vital** to replicate commands that change the data you are storing, however, is pointless and wasteful to replicate commands that do not apply any change to the data.
+The PRO version comes without telemetrics.
 
-You definitely want to replicate every INSERTs, UPDATEs or DELETEs while you should avoid replicating SELECTs.
+The community version requires RediSQL to periodically send telemetrics information to our server otherwise RediSQL shut itself down.
+This is not require by the PRO version.
 
-Replicated commands are usually executed either when you are re-loading your dataset after some sort of failures or in slaves/replica with a train of other replicated commands is coming right after.
+## Telemetrics data
 
-Consider what happens if you replicate a big SELECT. RediSQL is going to execute it and it is going to take some time, this while your application is waiting for redis to restart or when a train of replicated commands are piling up in the slaves/replicas buffers. And all this just for discard the result of the SELECT itself.
+The data send to our servers are definitely not critical data, indeed we ship the result of the `REDISQL.STATISTICS` commands.
+Moreover we took all the precaution to make sure that our user are not impacted by possible errors on our side replicating all pieces of our infrastructure. [More details about the technical implementation on our blog.][redisql-telemetrics]
 
-In order to avoid this effect is a good idea to use the query commands whenever possible ([`REDISQL.QUERY`][query] and [`REDISQL.QUERY_STATEMENT`][query_statement]), this command **do not** replicate and are marked as `readonly` which means that can be executed also on slaves/replicas providing interesting primitives of load balancing. (Eg. You could write on the master and read on the slaves.)
+[More details behind our motivation in our blog post.][release-1.0.0]
 
+[release-1.0.0]: http://redbeardlab.com/2019/04/09/redisql-release-1-0-0-change-in-strategy-and-business-model/
+[redisql-telemetrics]: http://redbeardlab.com/2019/04/09/telemetrics-for-redisql/
 [query]: references.md#redisqlquery
 [query_statement]: references.md#redisqlquery_statement
 [pro_motivations]: pro_motivations.md

doc/docs/pro_motivations.md

@@ -13,9 +13,7 @@ pages:
   -
     Pro: pro.md
   -
-    Motivations:
-      - "Motivations": motivations.md
-      - "PRO Motivations": pro_motivations.md
+    Motivations: motivations.md
   -
     Blog:
       - 'Release 0.9.0': 'blog/release_0.9.0.md'