I am extremely new to both the Rust ecosystem and to AWS Lambda; please excuse my naivety.
In my two hours of research on how I would use Rust on AWS Lambda, I felt repeatedly steered toward cargo-lambda.
Should this crate be used in addition to or instead ofcargo-lambda?
I'm tripped up with the handler function; it seems like cargo-lambda automatically sets up its idea of a handler function and lambda-web also provides a handler function (depending on the web framework being used). Does that mean that these two crates are incompatible?
This looks like a cool project, so I just wanted to extend my congratulations, even if I don't quite understand it all yet :sweat_smile:
EDIT: ah, wait, I might have figured it out; I'll update and potentially close this question soon.
I am extremely new to both the Rust ecosystem and to AWS Lambda; please excuse my naivety.
In my two hours of research on how I would use Rust on AWS Lambda, I felt repeatedly steered toward
cargo-lambda
.Should this crate be used in addition to or instead of
cargo-lambda
?I'm tripped up with the handler function; it seems like
cargo-lambda
automatically sets up its idea of a handler function andlambda-web
also provides a handler function (depending on the web framework being used). Does that mean that these two crates are incompatible?This looks like a cool project, so I just wanted to extend my congratulations, even if I don't quite understand it all yet :sweat_smile:
EDIT: ah, wait, I might have figured it out; I'll update and potentially close this question soon.