8 ms·

We are making these open source runtimes available soon: C++[1] Rust[2] We are also working with our partners to provide more open source runtimes: Erl

We are making these open source runtimes available soon: C++[1] Rust[2] We are also working with our partners to provide more open source runtimes: Erlang (Alert Logic) Elixir (Alert Logic) Cobol (Blu Age) N|Solid (NodeSource) PHP (Stackery) There is also native Ruby support as well[3] 1. https://aws.amazon.com/blogs/compute/introducing-the-c-lambda-runtime/ https://aws.amazon.com/blogs/compute/introducing-the-c-lambd... 2. https://aws.amazon.com/blogs/opensource/rust-runtime-for-aws-lambda/ https://aws.amazon.com/blogs/opensource/rust-runtime-for-aws... 3. https://aws.amazon.com/blogs/compute/announcing-ruby-support-for-aws-lambda/ https://aws.amazon.com/blogs/compute/announcing-ruby-support...

griffordson 8y ago
Thanks for sharing the Ruby links.
aantix 8y ago
Thanks for the Ruby links. With the native ruby support[3], I wonder how hard it would be to implement a Lambda ActiveJob handler..
- scarface74 8y ago
  Why would you need to make an active Job handler? What would that do for you over just a regular event based Ruby lambda? Honest question: I don’t Ruby, I just looked up what it is.
  - ryanmarsh 8y ago
    Instead of enquing a job you’d just write to an SQS queue and have a lambda as your “job handler” using the queue as an event source. Boom, no need for Active Job. Welcome to Serverless. There’s going to be a lot of people trying to do things the “rails way” on serverless and it’s going to be a little confusing for a while. Many will write it off, some will creat innovative new gems. And of course the Ruby community will come up with the best abstraction for SAM templates and deployment, because we like nice tools.
    - otterley 8y ago
      No need to use SQS here, assuming you don't need strict ordering behavior, since SNS can use Lambda functions as notification targets. The nice thing about SNS is that it can automatically fan out to multiple Lambda functions in parallel.
      - ryanmarsh 8y ago
        Indeed that is true, SNS can fan out to Lambda. It’s my understanding (I welcome a correction) that ActiveJob is more sequential like SQS + Lambda.
        scarface74 8y ago
        More like SQS -> Multiple lambda instances Unless you set the concurrency to one. But as always when working with any queue, don’t depend on only once processing or in order processing. AWS does have FIFO queues but they don’t work with lambda directly.
      - freedomben 8y ago
        Be careful the if there is possibility for a job to fail and need retry. SQS visibility and automatic dead lettering can give you this basically for free. I don't think SNS will.
        otterley 8y ago
        Lambda functions can be configured to use SNS for dead letter queues as well. See https://docs.aws.amazon.com/lambda/latest/dg/retries-on-errors.html https://docs.aws.amazon.com/lambda/latest/dg/retries-on-erro... (event sources that aren't stream-based).
        freedomben 8y ago
        Ah, very nice. Thanks for the correction.
      - 8y ago
  - dyeje 8y ago
    Most people use Sidekiq which uses Redis for ActiveJob. If there was an Lambda backend then you could get rid of Redis.
    - ryanmarsh 8y ago
      You won’t need Sidekiq either.
      - bpicolo 8y ago
        Sidekiq has other useful features (like the built in dashboard)
        scarface74 8y ago
        That’s what CloudWatch is for....
        jm547ster 8y ago
        CloudWatch is an awful tool to have to use
        scarface74 8y ago
        Don’t get me wrong, I’m no savage. I use structured JSON logging with Serilog and use ElasticSearch as a sink with a Kibanna for most of my app logging. I also log to Cloudwatch though and keep those logs for maybe a week.
      - dyeje 8y ago
        Yes, you wouldn't use Sidekiq anymore either because you would have a different ActiveJob backend, but the important part is that you're eliminating a piece of infrastructure (Redis) without the the poor scalability of DelayedJob.
    - deleted 8y ago
      [deleted]
danilop 8y ago
The post is now updated with links to the C++ and Rust runtimes, they are available now!
- steveklabnik 8y ago
  Awesome! I'm so excited to see this support. :D
- kevinSuttle 8y ago
  Woot! https://aws.amazon.com/blogs/opensource/rust-runtime-for-aws-lambda/ https://aws.amazon.com/blogs/opensource/rust-runtime-for-aws...
barbecue_sauce 8y ago
Guess I'll go learn Cobol now.
- rodgerd 8y ago
  You laugh, but depending on the actual Cobol support (e.g. whether it also supports a decent amount of CICS) it could make it easy to port a bunch of functions that are locked away on zOS.
  - barbecue_sauce 8y ago
    I was actually serious.
    - freedomben 8y ago
      That might be really smart. Cobol is still in wide use, and somebody needs to replace the aging Cobol community. I bet salaries will sky rocket
      - lostcolony 8y ago
        They already have. You're entering a market, as you say, where every contemporary is a super senior developer, for old, rich companies like banks, and with demand staying static...but supply dropping.
        jonathanpoulter 8y ago
        I've read this multiple times, and I'm sure it's an intuive argument. Is it actually true though?
        pjmlp 8y ago
        Yep, I am aware of projects currently looking for COBOL devs in Germany.
wpietri 8y ago
This is great, but I'm ever so slightly disappointed that they called it the Lambda Runtime API instead of Common Gateway Interface. [1] It's not quite the same, but it definitely gives me an everything-old-is-new-again feeling. https://en.wikipedia.org/wiki/Common_Gateway_Interface https://en.wikipedia.org/wiki/Common_Gateway_Interface
- kitd 8y ago
  Hmm, I was thinking Service Component Architecture [1], but yes, I can relate to your 2nd point. [1] https://en.wikipedia.org/wiki/Service_Component_Architecture https://en.wikipedia.org/wiki/Service_Component_Architecture
- fuball63 8y ago
  Interesting you mention CGI; I built https://bigcgi.com https://bigcgi.com (https://github.com/bmsauer/bigcgi https://github.com/bmsauer/bigcgi) primarily to address the issue of "any language" in FaaS environments. Seeing this takes away one of my biggest comparative advantages, but I'm happy to see that at least I was not wrong in thinking this feature would be important for developers. CGI still has the advantage of being an open standard, locally testable, and not vendor specific.

griffordson 8y ago

Thanks for sharing the Ruby links.

aantix 8y ago

Thanks for the Ruby links. With the native ruby support[3], I wonder how hard it would be to implement a Lambda ActiveJob handler..

scarface74 8y ago
Why would you need to make an active Job handler? What would that do for you over just a regular event based Ruby lambda? Honest question: I don’t Ruby, I just looked up what it is.
- ryanmarsh 8y ago
  Instead of enquing a job you’d just write to an SQS queue and have a lambda as your “job handler” using the queue as an event source. Boom, no need for Active Job. Welcome to Serverless. There’s going to be a lot of people trying to do things the “rails way” on serverless and it’s going to be a little confusing for a while. Many will write it off, some will creat innovative new gems. And of course the Ruby community will come up with the best abstraction for SAM templates and deployment, because we like nice tools.
  - otterley 8y ago
    No need to use SQS here, assuming you don't need strict ordering behavior, since SNS can use Lambda functions as notification targets. The nice thing about SNS is that it can automatically fan out to multiple Lambda functions in parallel.
    - ryanmarsh 8y ago
      Indeed that is true, SNS can fan out to Lambda. It’s my understanding (I welcome a correction) that ActiveJob is more sequential like SQS + Lambda.
      - scarface74 8y ago
        More like SQS -> Multiple lambda instances Unless you set the concurrency to one. But as always when working with any queue, don’t depend on only once processing or in order processing. AWS does have FIFO queues but they don’t work with lambda directly.
    - freedomben 8y ago
      Be careful the if there is possibility for a job to fail and need retry. SQS visibility and automatic dead lettering can give you this basically for free. I don't think SNS will.
      - otterley 8y ago
        Lambda functions can be configured to use SNS for dead letter queues as well. See https://docs.aws.amazon.com/lambda/latest/dg/retries-on-errors.html https://docs.aws.amazon.com/lambda/latest/dg/retries-on-erro... (event sources that aren't stream-based).
        freedomben 8y ago
        Ah, very nice. Thanks for the correction.
    - 8y ago
- dyeje 8y ago
  Most people use Sidekiq which uses Redis for ActiveJob. If there was an Lambda backend then you could get rid of Redis.
  - ryanmarsh 8y ago
    You won’t need Sidekiq either.
    - bpicolo 8y ago
      Sidekiq has other useful features (like the built in dashboard)
      - scarface74 8y ago
        That’s what CloudWatch is for....
        jm547ster 8y ago
        CloudWatch is an awful tool to have to use
        scarface74 8y ago
        Don’t get me wrong, I’m no savage. I use structured JSON logging with Serilog and use ElasticSearch as a sink with a Kibanna for most of my app logging. I also log to Cloudwatch though and keep those logs for maybe a week.
    - dyeje 8y ago
      Yes, you wouldn't use Sidekiq anymore either because you would have a different ActiveJob backend, but the important part is that you're eliminating a piece of infrastructure (Redis) without the the poor scalability of DelayedJob.
  - deleted 8y ago
    [deleted]

danilop 8y ago

The post is now updated with links to the C++ and Rust runtimes, they are available now!

steveklabnik 8y ago
Awesome! I'm so excited to see this support. :D
kevinSuttle 8y ago
Woot! https://aws.amazon.com/blogs/opensource/rust-runtime-for-aws-lambda/ https://aws.amazon.com/blogs/opensource/rust-runtime-for-aws...

barbecue_sauce 8y ago

Guess I'll go learn Cobol now.

rodgerd 8y ago
You laugh, but depending on the actual Cobol support (e.g. whether it also supports a decent amount of CICS) it could make it easy to port a bunch of functions that are locked away on zOS.
- barbecue_sauce 8y ago
  I was actually serious.
  - freedomben 8y ago
    That might be really smart. Cobol is still in wide use, and somebody needs to replace the aging Cobol community. I bet salaries will sky rocket
    - lostcolony 8y ago
      They already have. You're entering a market, as you say, where every contemporary is a super senior developer, for old, rich companies like banks, and with demand staying static...but supply dropping.
      - jonathanpoulter 8y ago
        I've read this multiple times, and I'm sure it's an intuive argument. Is it actually true though?
        pjmlp 8y ago
        Yep, I am aware of projects currently looking for COBOL devs in Germany.

wpietri 8y ago

This is great, but I'm ever so slightly disappointed that they called it the Lambda Runtime API instead of Common Gateway Interface. [1] It's not quite the same, but it definitely gives me an everything-old-is-new-again feeling. https://en.wikipedia.org/wiki/Common_Gateway_Interface https://en.wikipedia.org/wiki/Common_Gateway_Interface

kitd 8y ago
Hmm, I was thinking Service Component Architecture [1], but yes, I can relate to your 2nd point. [1] https://en.wikipedia.org/wiki/Service_Component_Architecture https://en.wikipedia.org/wiki/Service_Component_Architecture
fuball63 8y ago
Interesting you mention CGI; I built https://bigcgi.com https://bigcgi.com (https://github.com/bmsauer/bigcgi https://github.com/bmsauer/bigcgi) primarily to address the issue of "any language" in FaaS environments. Seeing this takes away one of my biggest comparative advantages, but I'm happy to see that at least I was not wrong in thinking this feature would be important for developers. CGI still has the advantage of being an open standard, locally testable, and not vendor specific.