Performant inmemory

[itrofimow]

This is more performant (well i hope so) version of #18

[Bobreshovr]

Provocation!!! 😄 What about liteDB?

[itrofimow]

Didn't have a close look at LiteDb, but i am not that sure it's any better - i mean, yes,

• it can persist the DB in a file, but is it really usable tho? - if someone needs to persist their jobsDB, then neither inMemory nor files aren't a good solution, point stands
• Indexes out of the box, covered with tests.. well, sure. But i believe that inMemory repo should not only be super easy to setup, but also (and not less important IMO) be as fast as possible. Are you sure LiteDb is more performant than this approach? You never know until you run a good load test :)

[Bounz]

Guys, don't you want to use https://github.com/dotnet/BenchmarkDotNet to measure performance improvements/deteriorations during the work on im-memory store?