LocalStack vs Serverless

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

LocalStack

47
122
+ 1
33
Serverless

1K
1.1K
+ 1
23
Add tool
Decisions about LocalStack and Serverless

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 LocalStack
Pros of Serverless
  • 4
    Integration with Python/nosetests
  • 4
    Local/offline testing
  • 4
    No dependency on cloud
  • 3
    Available as Docker image
  • 3
    Continuous integration
  • 3
    The correct URL is https://github.com/localstack/locals
  • 3
    Integration with Java/JUnit
  • 3
    Increases dev speed
  • 3
    Easy to use
  • 3
    Cost effective testing
  • 12
    API integration
  • 7
    Supports cloud functions for Google, Azure, and IBM
  • 2
    Lower cost
  • 1
    Openwhisk
  • 1
    Auto scale

Sign up to add or upvote prosMake informed product decisions

Cons of LocalStack
Cons of Serverless
  • 2
    Doesn't work well on Windows
  • 1
    No proper admin panel/web UI
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    What is LocalStack?

    LocalStack provides an easy-to-use test/mocking framework for developing Cloud applications.

    What is 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.

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

    What companies use LocalStack?
    What companies use Serverless?
    See which teams inside your own company are using LocalStack or Serverless.
    Sign up for StackShare EnterpriseLearn More

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

    What tools integrate with LocalStack?
    What tools integrate with Serverless?

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

    What are some alternatives to LocalStack and Serverless?
    OpenStack
    OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface.
    Minio
    Minio is an object storage server compatible with Amazon S3 and licensed under Apache 2.0 License
    AWS Amplify
    A JavaScript library for frontend and mobile developers building cloud-enabled applications. The library is a declarative interface across different categories of operations in order to make common tasks easier to add into your application. The default implementation works with Amazon Web Services (AWS) resources but is designed to be open and pluggable for usage with other cloud services that wish to provide an implementation or custom backends.
    AWS CLI
    It is a unified tool to manage your AWS services. With just one tool to download and configure, you can control multiple AWS services from the command line and automate them through scripts.
    AWS Shell
    The AWS Command Line Interface is a unified tool to manage your AWS services.
    See all alternatives