Wisen Tanasa

@srajat84 Yes it is aligned, because the long-lived connections is actually managed by AWS API Gateway. There are a couple of entry points where you can provide hooks to Lambdas,...

[This diagram from AWS](https://aws.amazon.com/blogs/compute/announcing-websocket-apis-in-amazon-api-gateway/) should give a high level overview: 

@hugosenari Thanks for the idea! One of the challenge on finding the connection is a developer might want to store the connection by multiple attributes. For example in a mobile...

Thanks for the suggestion @chris-kobrzak, how I have missed 33 Holborn! That's a good idea. I'm thinking that it should be in a blog, article, or laconia main home page....

@laconiajs/contributors Sorry I should have started this issue as a discussion. But it would be great if you can review the above public contract / API.

I have just discovered nestjs and really liked the decorator concept that it is using for JavaScript. See this example code from nestjs ```js import { Controller, Get, Post, Body,...

After a debate with @uncinimichel, I have counter-arguments for the usage decorator: - It's not appropriate to be used in application / use case level. If the principle is for...

On the point of being natural or not, I guess I wonder how much of nestjs users are actually using the JS version of its capability (versus TypeScript). I have...

Agreed, maybe this is too much of an overkill. Seems like the imperative approach would work. Are there disadvantages that we can think of?

@hugosenari Thanks for contributing here. I feel that `.on()` is more suitable towards events, and the mapping doesn't feel like one of it. It feels a little unnatural to include...