terraform-aws-lambda VS Flutter

There are just too many required parameters to create a single handler. And then you need to do that N times for each handler. Take a look at a complete Terraform example for a lambda: https://github.com/terraform-aws-modules/terraform-aws-lambd...

For a personal project it's just a bit much in my experience, especially since most personal projects can easily be served by a t3.micro.

https://github.com/terraform-aws-modules/terraform-aws-lambda/ - this modules has it all. There are various examples and submodules in that repository to help you achieve all your serverless tasks the same way.

It’s also weird not to know about terraform modules. There are a lot of things you _can_ configure because there are a lot of things people need to configure but if you’re using something like https://github.com/terraform-aws-modules/terraform-aws-lambd... it’s only a couple of lines of config for a Lambda.

I use the Community Terraform Lambda Module to define the lambda. It allows me to define a lambda in just a few lines that are configured with a role and can also be easily extended with policies. The cool thing is that cdktf supports a type import. To do this, simply add the following module to the cdktf.json file:

As somebody already mentioned in the comments, you can use the terraform-aws-lambda module as well as many other modules for typical serverless services like API Gateway v2, AppSync, EventBridge, StepFunctions, AppConfig, DynamoDB, and many more.

You can containerize the lambda functions and when you deploy each lambda function, you can overwrite the CMD for each function in the resource block to match what you need. I'm doing something similar but only deploy 2 lambda functions which use the same source code but do very different tasks. I also strongly suggest you use the terraform-aws-lambda module since it will build out all related resources you need.

Have a look at this module: https://github.com/terraform-aws-modules/terraform-aws-lambda

I can't find any open issues on github or anyone asking for it other than in the modules that are provided. https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/128

[3]: https://github.com/flutter/flutter/tree/master/packages/flut...

Thanks - that link does not appear to be open access, anyways I don't think I've seen it. I'm familiar with Flutter at a high-level (Kevin Moore gave a great talk on it at Wasm I/O), and I think other than requiring users to work in Dart, it is probably one of the most powerful ways to do cross-platform UI today.

Worth noting that their original GPU backend was Skia, and now they are retooling around Flutter GPU (Impeller)[0], which is kind of designed similarly as an abstract rendering interface over platform-specific GPU APIs.

[0]https://github.com/flutter/flutter/wiki/Flutter-GPU

If you are considering Electron/React then I would suggest adding Flutter to your list of technologies to consider. It uses Dart (a language similar to C#) and has a lot going for it… relatively quick to get up to speed with, fantastic developer experience (e.g., hot reload, great IDE support, good development tools) and very strong cross-platform support: it generates native iOS, Android, MacOS, Windows and Linux executables. Check it out: https://flutter.dev/

You can find the React Native documentation here and Flutter Documentation here.

[1]https://github.com/flutter/flutter/issues/55092#issuecomment...

> There is actually a great issue thread on the Flutter GitHub that explains exactly why other solutions do not work correctly when compared to hooks [0]

Interesting. I assume you are referring to this comment in particular -> https://github.com/flutter/flutter/issues/51752#issuecomment... ?