Cloud storage was just used so I didn&#x27;t have to manage backups myself.<p>I absolutely didn&#x27;t separate command and query - the commands themselves are actions which execute against the domain model, and that domain is used to build responses.<p>My project is here: [Sourcery](<a href="https:&#x2F;&#x2F;github.com&#x2F;mcintyre321&#x2F;Sourcery" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;mcintyre321&#x2F;Sourcery</a>) but I think a more mature project you might like to look into is [OrigioDB](<a href="http:&#x2F;&#x2F;origodb.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;origodb.com&#x2F;</a>).<p>Another thing that gets tricky is making your application deterministic - any calls to the current time, random number or guid generatiom, or to 3rd party services, have to be recorded and replayable in the correct order for when you reconstruct your application instance. This can get tricky if you refactor your application or change its logic later.<p>It&#x27;s worth reading up on Prevalence&#x2F;MemoryImage, and looking into NEventStore also.