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

AWS Lambda

17.3K
13.1K
+ 1
418
Sidekiq

1K
554
+ 1
407
Add tool

AWS Lambda vs Sidekiq: What are the differences?

AWS Lambda: Automatically run code in response to modifications to objects in Amazon S3 buckets, messages in Kinesis streams, or updates in DynamoDB. 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; Sidekiq: Simple, efficient background processing for Ruby. Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.

AWS Lambda can be classified as a tool in the "Serverless / Task Processing" category, while Sidekiq is grouped under "Background Processing".

"No infrastructure", "Cheap" and "Quick" are the key factors why developers consider AWS Lambda; whereas "Simple", "Efficient background processing" and "Scalability" are the primary reasons why Sidekiq is favored.

Sidekiq is an open source tool with 9.68K GitHub stars and 1.66K GitHub forks. Here's a link to Sidekiq's open source repository on GitHub.

9GAG, Asana, and CircleCI are some of the popular companies that use AWS Lambda, whereas Sidekiq is used by StackShare, Product Hunt, and HotelTonight. AWS Lambda has a broader approval, being mentioned in 1023 company stacks & 613 developers stacks; compared to Sidekiq, which is listed in 348 company stacks and 77 developer stacks.

Decisions about AWS Lambda and Sidekiq

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 Private StackShare. Sign up for Private StackShare.
Learn More
Pros of AWS Lambda
Pros of Sidekiq
  • 127
    No infrastructure
  • 82
    Cheap
  • 69
    Quick
  • 57
    Stateless
  • 47
    No deploy, no server, great sleep
  • 9
    AWS Lambda went down taking many sites with it
  • 6
    Event Driven Governance
  • 5
    Auto scale and cost effective
  • 5
    Extensive API
  • 5
    Easy to deploy
  • 4
    VPC Support
  • 2
    Integrated with various AWS services
  • 123
    Simple
  • 99
    Efficient background processing
  • 60
    Scalability
  • 37
    Better then resque
  • 26
    Great documentation
  • 15
    Admin tool
  • 14
    Great community
  • 8
    Integrates with redis automatically, with zero config
  • 7
    Great support
  • 7
    Stupidly simple to integrate and run on Rails/Heroku
  • 3
    Freeium
  • 3
    Ruby
  • 2
    Pro version
  • 1
    Fast
  • 1
    Dashboard w/live polling
  • 1
    Great ecosystem of addons

Sign up to add or upvote prosMake informed product decisions

Cons of AWS Lambda
Cons of Sidekiq
  • 5
    Cant execute ruby or go
  • 0
    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 Sidekiq?

    Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.

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

    What companies use AWS Lambda?
    What companies use Sidekiq?
    See which teams inside your own company are using AWS Lambda or Sidekiq.
    Sign up for Private StackShareLearn More

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

    What tools integrate with AWS Lambda?
    What tools integrate with Sidekiq?

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

    Blog Posts

    Jun 6 2019 at 5:11PM

    AppSignal

    RedisRubyKafka+9
    15
    1216
    GitHubPythonNode.js+47
    50
    69616
    GitHubDockerAmazon EC2+23
    12
    6377
    JavaScriptGitHubPython+42
    52
    19985
    What are some alternatives to AWS Lambda and Sidekiq?
    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