Hi everyone, I have another question. I noticed the GMS uses ComplexKeyResourceTask template underneath, yet I did not find any asynchronous implementations. Is there a particular reason why the async resource template was chosen over the synchronous one? Are there any plans for an async DAO for instance?

Great question. Here are some doc on async resource: https://linkedin.github.io/rest.li/user_guide/restli_server#asynchronous-resources With the current simple key-value retrieval pattern it doesn't actually matter if it's sync or async. However, should an endpoint choose to implement complex biz logic, it could potentially leverage parseq to parallelize multiple operations to improve performance.