Local testing has improved containerized AWS workflows and supports fast proof of concept builds
What is our primary use case?
My main use case for
LocalStack is for tests on my machine. For example, when I want to create a table in
AWS, I create a
LocalStack and use it in my tests before I publish the
Terraform. I also create my application container and create the tables in LocalStack for running all my tests. I use not only tables, but also SQS and SNS. I only have features that I use to add about my main use case for LocalStack, to be honest.
What is most valuable?
The best features LocalStack offers are DynamoDB and container tests. I use a lot of testing containers, and it has helped me significantly.
LocalStack helps me with containers because it is easy to configure. I write my tests and when I need to deploy an application, all my tests are running in my pipeline through my DevOps process, and I can guarantee there is quality in my code. I have a container with LocalStack testing everything.
LocalStack has positively impacted my organization by improving the quality of the software and allowing us to test comprehensively.
What needs improvement?
I really do not have an opinion right now about how LocalStack can be improved because for my use, the features that I use are perfect. There may be many features that I have not used. Everyone here uses the same features that I use, so I cannot add more about needed improvements. It is pretty easy to use.
For how long have I used the solution?
I have been using LocalStack for about two years.
What was our ROI?
I have not seen any return on investment for myself on my machine.
What's my experience with pricing, setup cost, and licensing?
I do not know about the pricing, setup cost, and licensing for LocalStack because I just use it for myself. I do not use LocalStack in the production environment, only for myself to do my tests.
What other advice do I have?
For example, sometimes I just do a proof of concept. Instead of creating a Terraform and publishing on AWS and having to create my table and my query over there, I do not need to do everything when doing a proof of concept on my machine. It has helped me a lot. I create a LocalStack and everything is working.
For the features that I use, I would say LocalStack deserves a 10 because I do not use any other features. I give LocalStack a 10 because it is pretty easy. I run my container on my machine and everything is working. It is pretty easy to create an SQS and SNS. For the features that I use, it is perfect and easy. I rate this review a 10.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Set up can require some fiddling but once it's working it's great
What do you like best about the product?
LocalStack helps emulate resources in your local environment. For us, it has been very useful in mocking AWS resources for local development and makes that workflow easier as we don't have to maintain our own custom solution.
What do you dislike about the product?
LocalStack doesn't entirely have feature parity and can sometimes be a bit fiddly to set up. It requires a lot fo reading through docs and debugging to get going.
What problems is the product solving and how is that benefiting you?
LocalStack is helping our development workflow by allowing us to mock resources and therefore ensures fast development as we can run and debug changes locally before rolling them out to other environments.