My main use case for LocalStack is to run AWS services locally on our machines, such as running on our laptop or on our server, and for a sandbox for testing our cloud apps.
A quick, specific example of how I use LocalStack for testing my cloud apps is that we use LocalStack for a sandbox or staging environment for AWS resources. We test it on LocalStack, and if everything works well, then we deploy it to AWS.
The best features LocalStack offers include the ability to test everything locally at no cost for AWS, a faster development and instant feedback cycle, offline deployment without needing internet, and it's excellent for learning AWS in a sandbox environment.
Out of those features, I find myself relying on the ability to run it locally for testing at no cost the most.
Using LocalStack has positively impacted my organization by saving 50-60% of our money because of using LocalStack and AWS resources on our local environment.
I calculated that 56% savings mostly on infrastructure cycle because if we use AWS, we have to pay for those resources, but by using LocalStack, we do not need to provision resources on AWS, so that is how we are saving that percentage.
LocalStack can be improved as it is currently not fully compatible with AWS services in each case, and there are limited features right now in that service. Additionally, only some of the services are free, and sometimes things work on LocalStack locally but fail on AWS. There is a performance limit, so I want those things to get improved.
I have been using LocalStack for six months.
In my experience, LocalStack is stable.
LocalStack's scalability is good.
I have seen a return on investment as I mentioned. We are saving 50 to 60% of our money using it.
My experience with pricing, setup cost, and licensing is that we are not currently paying for LocalStack, and the setup is easy. You just need to install Docker.
Before choosing LocalStack, we had a clear mindset that we wanted to use it.
I would rate this product an 8 out of 10.