Added stub project outlining rationale and high-level ideas on Redis-based Actors.
This is just too much of stuff: Async + concurrent distributed locks via 3rd party library via Task<>... Undebugable and mind blowing , probably waste of time. Current state is all way buggy! Should just hide normal lock via setnx behind target Async API and Async.Sleep with capped exp intervals
RunSynchronously instead of StartImmediate
Merge branch 'develop'

Conflicts:
	RELEASE_NOTES.md
	src/Fredis/AssemblyInfo.fs
	src/Fredis/Connection.fs
	src/Fredis/Fredis.fsproj
	src/Fredis/Script.fsx
	tests/Fredis.Tests/Tests.fs
	tests/Fredis.Tests/Tests.fsx
Thoughts dump
save current work
Adding persistence stuff to caching/redis stuff since they use the same objects. This commit adds a typed DB persistor with a simple sharding strategy similar to Pinterest's one but with Guids and without moving data ever, really (data stays on the same physical shard forever, in case of AWS will need only downtime for resizing and that is it).

The goal is to put together very simple APIs to work with POCOs and files and make it scalable at least to some moderate size to win time when single boxes could choke (using AWS as a base case).

TODO: files, queues, cache client; think about DynamoDB/ElasticSearch as separate IPocoPersistors or a single one which dispatches by attributes