Alternatives to LocalStack logo

Alternatives to LocalStack

Serverless, OpenStack, Minio, AWS Amplify, and AWS CLI are the most popular alternatives and competitors to LocalStack.
43
114
+ 1
33

What is LocalStack and what are its top alternatives?

LocalStack provides an easy-to-use test/mocking framework for developing Cloud applications.
LocalStack is a tool in the AWS Tools category of a tech stack.
LocalStack is an open source tool with 175 GitHub stars and 36 GitHub forks. Here’s a link to LocalStack's open source repository on GitHub

Top Alternatives to LocalStack

  • Serverless
    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. ...

  • OpenStack
    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

    Minio is an object storage server compatible with Amazon S3 and licensed under Apache 2.0 License ...

  • AWS Amplify
    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
    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
    AWS Shell

    The AWS Command Line Interface is a unified tool to manage your AWS services. ...

  • troposphere
    troposphere

    The troposphere library allows for easier creation of the AWS CloudFormation JSON by writing Python code to describe the AWS resources. troposphere also includes some basic support for OpenStack resources via Heat. ...

  • awless
    awless

    awless is a fast, powerful and easy-to-use command line interface (CLI) to manage Amazon Web Services. ...

LocalStack alternatives & related posts

Serverless logo

Serverless

1.4K
1.1K
23
The most widely-adopted toolkit for building serverless applications
1.4K
1.1K
+ 1
23
PROS OF SERVERLESS
  • 12
    API integration
  • 7
    Supports cloud functions for Google, Azure, and IBM
  • 2
    Lower cost
  • 1
    Openwhisk
  • 1
    Auto scale
CONS OF SERVERLESS
    Be the first to leave a con

    related Serverless posts

    Praveen Mooli
    Engineering Manager at Taylor and Francis · | 17 upvotes · 2.3M views

    We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

    To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

    To build #Webapps we decided to use Angular 2 with RxJS

    #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

    See more
    Nitzan Shapira

    At Epsagon, we use hundreds of AWS Lambda functions, most of them are written in Python, and the Serverless Framework to pack and deploy them. One of the issues we've encountered is the difficulty to package external libraries into the Lambda environment using the Serverless Framework. This limitation is probably by design since the external code your Lambda needs can be usually included with a package manager.

    In order to overcome this issue, we've developed a tool, which we also published as open-source (see link below), which automatically packs these libraries using a simple npm package and a YAML configuration file. Support for Node.js, Go, and Java will be available soon.

    The GitHub respoitory: https://github.com/epsagon/serverless-package-external

    See more
    OpenStack logo

    OpenStack

    674
    1K
    120
    Open source software for building private and public clouds
    674
    1K
    + 1
    120
    PROS OF OPENSTACK
    • 48
      Private cloud
    • 37
      Avoid vendor lock-in
    • 21
      Flexible in use
    • 6
      Industry leader
    • 4
      Supported by many companies in top500
    • 4
      Robust architecture
    CONS OF OPENSTACK
      Be the first to leave a con

      related OpenStack posts

      Minio logo

      Minio

      330
      507
      37
      AWS S3 open source alternative written in Go
      330
      507
      + 1
      37
      PROS OF MINIO
      • 8
        Store and Serve Resumes & Job Description PDF, Backups
      • 5
        S3 Compatible
      • 4
        Simple
      • 4
        Open Source
      • 3
        Encryption and Tamper-Proof
      • 2
        Highly Available
      • 2
        Pluggable Storage Backend
      • 2
        Lambda Compute
      • 2
        Private Cloud Storage
      • 2
        Scalable
      • 2
        Data Protection
      • 1
        Performance
      CONS OF MINIO
      • 2
        Deletion of huge buckets is not possible

      related Minio posts

      AWS Amplify logo

      AWS Amplify

      413
      482
      13
      JavaScript Open Source Library with React, React Native Extensions
      413
      482
      + 1
      13
      PROS OF AWS AMPLIFY
      • 4
        GraphQL
      • 3
        Better with Relations and Security
      • 2
        Flexible Auth options
      • 2
        Cheaper
      • 1
        Continuous deployment
      • 1
        Backed by Amazon
      CONS OF AWS AMPLIFY
      • 2
        Free tier is limited
      • 1
        Steep Learning Curve

      related AWS Amplify posts

      I am currently working on a long term mobile app project. Current stack: Frontend: Dart/Flutter Backend: Go, AWS Resources (AWS Lambda, Amazon DynamoDB, etc.) Since there are only two developers and we have limited time and resources, we are looking for a BAAS like Firebase or AWS Amplify to handle auth and push notifications for now. We are prioritizing developing speed so we can iterate quickly. The only problem is that AWS amplify support for flutter is in developer preview and has limited capabilities (We have tested it out in our app). Firebase is the more mature option. It has great support for flutter and has more than we need for auth, notifications, etc. My question is that, if we choose firebase, we would be stuck with using two different cloud providers. Is this bad, or is this even a problem? I am willing to change anything on the backend architecture wise, so any suggestions would be greatly appreciated as I am somewhat unfamiliar with Google Cloud Platform. Thank you.

      See more

      I am now building a React Native app, and I don't know what to choose for my backend between AWS Amplify and Firebase. Which one fits more with react native?

      See more
      AWS CLI logo

      AWS CLI

      118
      87
      0
      Universal Command Line Interface for Amazon Web Services
      118
      87
      + 1
      0
      PROS OF AWS CLI
        Be the first to leave a pro
        CONS OF AWS CLI
          Be the first to leave a con

          related AWS CLI posts

          AWS Shell logo

          AWS Shell

          33
          61
          0
          An integrated shell for working with the AWS CLI (by AWS)
          33
          61
          + 1
          0
          PROS OF AWS SHELL
            Be the first to leave a pro
            CONS OF AWS SHELL
              Be the first to leave a con

              related AWS Shell posts

              troposphere logo

              troposphere

              23
              26
              0
              Library to create AWS CloudFormation descriptions
              23
              26
              + 1
              0
              PROS OF TROPOSPHERE
              • 0
                Infrastructure as code
              CONS OF TROPOSPHERE
                Be the first to leave a con

                related troposphere posts

                awless logo

                awless

                19
                63
                8
                A Mighty CLI for AWS
                19
                63
                + 1
                8
                PROS OF AWLESS
                • 3
                  Easy Setup
                • 3
                  Powerful commands to access any AWS service
                • 2
                  An intuitive UI of output
                CONS OF AWLESS
                  Be the first to leave a con

                  related awless posts