⚡ <5ms Response Time Challenge

[keinsell]

The challenge to create a HTTP Server in JavaScript/TypeScript that will be able to handle single request in less than 5ms in local environment, the such server such include connection to database, authentication and overall end-to-end returning information to user. For learning purposes this can be extended to writing a simple HTTP in Golang and comparing it to Node.js.

• Up to this date server written in Nest.js and Express.js serves out a 40ms delay as codebase delay from Nest.js and 20ms from Express.js where code itself is able to run in like 3ms. This shows up the platform is fucked up and I belive this can be done much better in multiple ways.
• Archiving minimal latency in application will require implementation of cache and optimizing database connection handling.

Overall recommendedations for API is to response in less than 100ms to provide "instant" feeling to user as so will be standard I choose.

• https://stackoverflow.com/questions/164175/what-is-considered-a-good-response-time-for-a-dynamic-personalized-web-applicat
• https://hyperping.io/blog/what-is-a-good-api-response-time
• https://sematext.com/glossary/api-response-time/
• https://blog.sentry.io/whats-the-difference-between-api-latency-and-api-response-time/

---

• https://github.com/GetRayo/rayo.js
• https://www.npmjs.com/package/0http
• https://github.com/BackendStack21/restana
• https://web-frameworks-benchmark.netlify.app/result?asc=1&f=feathersjs,0http,koa,nestjs-express,express,sails,fastify,nestjs-fastify,restana&metric=averageLatency&order_by=level512
• https://github.com/the-benchmarker/web-frameworks/blob/37f10ec284cad74552ad3012b51165c74fdbba54/README.md?source=post_page-----1ee5285ce66-------------------------------

[keinsell]

So far the best potential solution I've found is hyper-express

[keinsell]

https://www.techempower.com/benchmarks/#hw=ph&test=json&section=data-r22&l=yyku7z-cn3

I think Node is not that bad, maybe if we combine Deno or Bun with things like hyper-express and build a little more improvements to typesystem on top of that (ex. how deepkit made bytecode typings) we can have really nice thing that will be productive.

The least performant things in JS are validation and serialization, so once solutions for these problems will be found it can definitely be better than express.js - but I would like to keep a compatiblity layer between express.js and fastify (through proxies)