Ts.ED
Replies: 1 comment 11 replies
-
|
Hello @ygyg70 Has I explained on slack:
Your approach seems to be different from the Serverless tutorial https://tsed.io/tutorials/serverless.html#configuration This is clearly not ideal and efficient. Your proposition seems to be more interesting but there is not example for that. The main idea is to have on handler/aws lambda that invoke the Ts.ED DI (https://github.com/tsedio/tsed/tree/production/packages/di): my-handler.ts import {InjectorService, attachLogger, DIContext} from "@tsed/di";
import {$log} from "@tsed/logger";
import {MyService} from "../usecases/MyService";
async function bootstrap(Service) {
const injector = new InjectorService();
// configure the default logger
attachLogger(injector, $log);
// Load all providers registered via @Injectable decorator
await injector.load();
// emit event to trigger actions for third parties modules
await injector.emit("$onReady");
return injector
}
const promise = bootstrap(); // to pre build Container before lambda handler invokation
export default async function handler(awsArgs) { // need to be completed
const injector = await promise
const ctx = new DIContext({
id: /* aws request.id || */ uuid.v4(),
injector,
logger: injector.logger
})
ctx.set("aws_args", awsArgs) // customise that to you convenient
const myService = injector.get<MyService>(MyService);
// we need to map aws Args to keep our MyService agnostic from AWS /!\ important
// and to reuse MyService inside a Ts.ED controller (clean architecture)
const {value, other} = mapAwsArg(AwsArgs);
try {
const response = await runInContext(ctx, () => myService.doSomething(value, other));
return mapResponseToAws(response)
} catch(er) {
// handle response
}
} Tell me if you have some question ;) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks!
Need to choose between SAM and paid version of LocalStack, SAM vs Terraform/other IaC, Serverless framework etc. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @ygyg70 His learning Curve is much better than NestJS. This is a positive point that comes up the most from companies and developers who have chosen the framework. I prefer to encourage the community to gives answer but I'm always available to give you answer. So in most time you have a answers during my working day. I take a time to create open source repository to gives basic examples between two frameworks. Sometimes I even take the time to review open-source project code based on Ts.ED and which is used for commercial purposes. But for Enterprise projects, I propose a sponsors tiers. Isn't enough but the gain is interesting for the company and me:
Right now, I understand that you need to benchmark each framework to choose the most valuable for you ;) I can propose you to take a time to review your open source repository and try to gives you some feedback. It's the least I can do to convince you ;) See you |
Beta Was this translation helpful? Give feedback.
-
|
Going through your changes and trying to understand. Node, ES, TS, module management and tooling are quite a chore to master.. |
Beta Was this translation helpful? Give feedback.
-
|
XD. I understand that the example repo is a little obscure (it lacks clarification). But your requests were to have a project taking advantage of tree shaking, executable/testable locally and which generates swagger. That's exactly what I did :) and more:
This is exactly my first point when you ask me ;). But even if you're doing pure JS, don't put an express server behind it. Uses Serverless + JS handlers. You will have everything you need to structure your project and have the performance. Note: I already tried a similar tools like aws-lambda-web-adapter (packages/platform/platform-serverless-http/src/builder/PlatformServerlessHttp.ts and the problem isn't the cold start (not really) but the fact that the developers think they are in a classic Node.js Express application when it is completely wrong! It's like telling a React developer that React-native is the same ;) Because a lambda is not written and should not be written like a Rest application. There are use cases where Lambda + Express will work:
But in this case, use Serveless configuration file is more interesting. Why Serverless ?Because it's a framework compatible with many cloud provider. It's really an advantage to keep your code portable to another cloud provider (if you do the right division at the code level (Clean archi, DDD, etc...). Also other points:
You'll have understood but my main point is do not use Express/Koa for your project it will not bring you anything, if you use the right tools to emulate your lambdas locally. ;) See you guy and thanks to have give me the opportunity to create a good tsed-aws-lambda project example |
Beta Was this translation helpful? Give feedback.
-
|
All this information and work are very useful :) |
Beta Was this translation helpful? Give feedback.
-
Before creating my own build configuration (probably something like), I wanted to ask if there is already something out there I can use.
(or perhaps someone is kind enough to share their approach)
Any help appreciated!
Beta Was this translation helpful? Give feedback.
All reactions