feat(di): add DIContext.PLATFORM property to distinguish the current platform runtime

[Romakita]

Information

Type	Breaking change
Feature	Yes

---

• Tests
• Coverage
• Example
• Documentation

[github-actions]

Benchmarks

• Machine: linux x64 | 4 vCPUs | 15.6GB Mem
• Node: v18.20.3
• Run: Wed Jun 19 2024 19:09:05 GMT+0000 (Coordinated Universal Time)
• Method: autocannon -c 100 -d 10 -p 10 localhost:3000 (two rounds; one to warm-up, one to measure)

	Version	Router	Requests/s	Latency	Throughput/Mb
koa	2.13.4	✗	33574.4	29.25	5.99
tsed-koa	7.72.0	✓	11904.4	83.23	10.08
express	4.19.2	✓	10622.9	93.33	1.89
nest	8.4.3	✓	9806.7	101.07	2.36
express-injector	4.19.2	✗	9503.8	104.28	2.17
tsed-express	7.72.0	✓	8567.8	115.69	1.57
express-morgan	4.19.2	✗	5678.0	174.44	1.01
fastify-big-json	3.29.4	✓	N/A	N/A	N/A
fastify-injector	3.29.4	✓	N/A	N/A	N/A
fastify	3.29.4	✓	N/A	N/A	N/A
nest-fastify	8.4.3	✓	N/A	N/A	N/A

Explanation

The benchmark shows a performance difference between the frameworks. We note that Ts.ED is often last. In fact, Ts.ED uses features useful to a production application which reduce its performance.

For example, Ts.ED initializes a sandbox (async_hook) for each request in order to work in an isolated context if necessary.
It also initializes the elements necessary for monitoring requests in a log manager.

All this at a necessary cost that reflects the reality of a production application ;)

[Romakita]

🎉 This PR is included in version 7.73.0 🎉

The release is available on:

• v7.73.0
• GitHub release

Your semantic-release bot 📦🚀