4 ms·
the other alternative is to just implement the go-aws-lambda protocol. it is basically a bunch of go RPC calls that AWS makes to a port that you listen on. if y
by benmmurphy 8y ago
the other alternative is to just implement the go-aws-lambda protocol. it is basically a bunch of go RPC calls that AWS makes to a port that you listen on. if you do it correctly it should be safe to run because AWS can't change the protocol in a way that is not backwards compatible with existing go projects. any language that can compile statically and be run on linux can run on AWS lambda because static-go binaries can be deployed to AWS lambda.
but this is probably a little less riskier because i'm sure if AWS made a change to the go protocol they would test it against their existing go libraries they have published but they can't test it against your <insert language> implementation.
- lvh 8y agoThe RPC mechanism uses Gob, not something like gRPC, so first you’d have to write a Gob parser. It’s not clear to me that that’s better.
- CSDude 8y agoYeah, I already mentioned that in the blog, Although Gob is simple enough, this was better as an experiment. But implementing Gob would be more mature choice in the long run.
- curun1r 8y ago> any language that can compile statically and be run on linux Most languages that satisfy this criteria can also speak the C ABI. So why not write a native module for Node, Python or Java? Dealing with those interfaces is faster and they're better standardized. FWIW.../me is running Rust on lambda as a Node native module.