So I'm writing what I'd use right now. :) It's not yet quite done enough for public consumption but it's an app framework, rather than a web framework, and it e

So I'm writing what I'd use right now. :) It's not yet quite done enough for public consumption but it's an app framework, rather than a web framework, and it expresses its HTTP layer through a facet that uses Fastify as its web server. It also includes an "event responder" facet for responding to events off of an event bus, a Redis queue, etc., and it's all wrapped up with a dependency injector that bears more similarities to a real one (dependency injection rather than module-welding service location) than to Angular's. The key structural difference to me is that there's a unified way for all of these systems to interrelate in a way that you see more with a mature framework like Spring Boot, over less mature tools like NestJS. I'm agnostic as to ORM layers but both Objection and TypeORM are worthy of consideration. My project's DI container will play nicely with both--it supports dynamic scopes and so it's really easy to do something like "create a transaction scope and request a service from it, and that service automatically wires up transition-backed TypeORM repositories." Which is hard, hard sledding in existing systems. I hope to open source it relatively soon.