TransactionalDOWrapper suggestions thread

Cool idea 👍 ! I recommend checking out do-transactional-outbox for an even stronger model of storage consistency. For your example in the blog post, I'm not sure if by using await you potentially eliminate (some of) the benefits of caching state in memory, let me explain. I recommend taking a look at state.blockConcurrencyWhile: call it in your constructor, no need to await it (you couldn't anyways, since constructors have to be sync), but it blocks further requests until you finish with your hydrate function. Then, you can always be sure that this.name and others will have been populated whenever your request comes in via fetch, so you can simplify your code further - eliminating another potential concurrency issue, where you're awaiting the hydrate promise, and another event handler starts executing, calling hydrate again, and potentially reading from storage once more as this.hydrated may not have been set to true yet (knock knock, race condition, who's there type situation), and then you overwrite name from the second call. Basically, use blockConcurrencyWhile in the constructor, move hydrate to within that call and remove it from fetch. Oh, small note, you could reduce boilerplate by exporting a function instead of a class, which applies the argument as the static class and returns that as the DO class for the runtime