> So how can we take a method call, serialise it, perhaps store it in a database, and then later rehydrate and execute?<p>Any messaging queue would be better. Yes it's easy to setup. No it doesn't require additional complexity (in fact, it's less complex than the proposed solution)<p>example: <a href="https://www.rabbitmq.com/tutorials/tutorial-one-dotnet#receiving" rel="nofollow">https://www.rabbitmq.com/tutorials/tutorial-one-dotnet#recei...</a>