Need advice about which tool to choose?Ask the StackShare community!

AWS Lambda

23.6K
18.4K
+ 1
432
s3-lambda

4
64
+ 1
0
Add tool
Decisions about AWS Lambda and s3-lambda
Tim Nolet

When adding a new feature to Checkly rearchitecting some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda . The short story:

  • Developer Experience trumps everything.
  • AWS Lambda is cheap. Up to a limit though. This impact not only your wallet.
  • If you need geographic spread, AWS is lonely at the top.
The setup

Recently, I was doing a brainstorm at a startup here in Berlin on the future of their infrastructure. They were ready to move on from their initial, almost 100% Ec2 + Chef based setup. Everything was on the table. But we crossed out a lot quite quickly:

  • Pure, uncut, self hosted Kubernetes β€” way too much complexity
  • Managed Kubernetes in various flavors β€” still too much complexity
  • Zeit β€” Maybe, but no Docker support
  • Elastic Beanstalk β€” Maybe, bit old but does the job
  • Heroku
  • Lambda

It became clear a mix of PaaS and FaaS was the way to go. What a surprise! That is exactly what I use for Checkly! But when do you pick which model?

I chopped that question up into the following categories:

  • Developer Experience / DX πŸ€“
  • Ops Experience / OX πŸ‚ (?)
  • Cost πŸ’΅
  • Lock in πŸ”

Read the full post linked below for all details

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of AWS Lambda
Pros of s3-lambda
  • 129
    No infrastructure
  • 83
    Cheap
  • 70
    Quick
  • 59
    Stateless
  • 47
    No deploy, no server, great sleep
  • 12
    AWS Lambda went down taking many sites with it
  • 6
    Event Driven Governance
  • 6
    Extensive API
  • 6
    Auto scale and cost effective
  • 6
    Easy to deploy
  • 5
    VPC Support
  • 3
    Integrated with various AWS services
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of AWS Lambda
    Cons of s3-lambda
    • 7
      Cant execute ruby or go
    • 3
      Compute time limited
    • 1
      Can't execute PHP w/o significant effort
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions

      - No public GitHub repository available -

      What is AWS Lambda?

      AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

      What is s3-lambda?

      s3-lambda enables you to run lambda functions over a context of S3 objects. It has a stateless architecture with concurrency control, allowing you to process a large number of files very quickly. This is useful for quickly prototyping complex data jobs without an infrastructure like Hadoop or Spark.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use AWS Lambda?
      What companies use s3-lambda?
        No companies found
        See which teams inside your own company are using AWS Lambda or s3-lambda.
        Sign up for StackShare EnterpriseLearn More

        Sign up to get full access to all the companiesMake informed product decisions

        What tools integrate with AWS Lambda?
        What tools integrate with s3-lambda?

        Sign up to get full access to all the tool integrationsMake informed product decisions

        Blog Posts

        GitHubPythonNode.js+47
        54
        72320
        GitHubDockerAmazon EC2+23
        12
        6566
        JavaScriptGitHubPython+42
        53
        21866
        What are some alternatives to AWS Lambda and s3-lambda?
        Serverless
        Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.
        Azure Functions
        Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.
        AWS Elastic Beanstalk
        Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.
        AWS Step Functions
        AWS Step Functions makes it easy to coordinate the components of distributed applications and microservices using visual workflows. Building applications from individual components that each perform a discrete function lets you scale and change applications quickly.
        Google App Engine
        Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.
        See all alternatives