docs improvement - "advanced section"

[ORESoftware]

At the moment, I am curious how domains are implemented with the newish AsyncHooks / AsyncListener API.
It might be a tad dangerous to leak details, but could there be an advanced section in the docs that does some case studies and talks about "under the hood" stuff and "implementation details"?

Right now, I am just curious how domain is implemented using AsyncHooks / AsyncListener and if it could be documented. TMK the domain implementation changed after AsyncHooks was introduced.

[jasnell]

A separate guide document that goes into the details would likely be a great addition.
/cc @nodejs/async_hooks

[ORESoftware]

bump

[Trott]

Someone on @nodejs/async_hooks please correct me if I'm wrong, but I don't think async_hooks development is active. I think we are now stuck supporting both deprecated domains and experimental async_hooks with no plausible scenario of dropping either in the foreseeable future.

Theoretically, since async_hooks is experimental, we could plausibly remove it. In practice, I don't think that's feasible given ecosystem usage, but I don't pay too close attention to either async_hooks or domain so I could be wrong.

[Flarna]

I think async hooks development is similar active as http development. There are no new features in pipeline to my knowledge but if there are bugs or other issues there is usually someone looking into it.
The last topics done in that area were to add AsyncLocalStore on top of it and to improve performance in tracking promises.

We can't remove the functionality itself as it's used by domains and AsyncLocalStore which are not experimental. We could remove the public API surface but as you said it would break quite a lot for mostly no benefit. There were discussions somewhere to mark it as something else then experimental. Not deprecated, maybe internal but as of now there is no official term to be used for modules like this.