alt Hacker NewsI evangelized localstack at my company a while back, but as we integrated it deeper into our CI test runs we started running into more and more things they don't support, and it feels impossible to get any attention from their support/devs despite being paying customers.
Their Cloud Pod and ephemeral instance features in particular feel pretty half-baked and not very useful at the moment.
Fun tangent: it's pretty easy to write a crack for the pro version; we actually used that for about a month as a pilot to confirm that it would do what we needed it to.
Replies
Which services weren't supported in your use case? Currently with our enterprise contract we use all the usual suspects:
AppConfig, DynamoDB, ElastiCache, Kinesis streams, RDS/Aurora with innodb engine, S3, SecretsManager, SNS, and SQS. I'm probably forgetting a few, but we haven't hit anything unsupported (yet.)
I also haven't touched any pod stuff and have no plans to. Probably just luck of the draw we didn't hit any holes or issues, but we tend not to use any esoteric features in AWS land.
I too was excited about the idea originally but then started realizing that they will have an increasingly untenable service area to try and maintain and mimic and it was just never going to work out.
[dead]
I used some small parts of localstack a long time back for some integration tests. I haven't kept up with what it does.
Looking at their pricing tiers, it seems that their paid product now a cloud based service, or partly cloud based.
I don't really see why you would pay to use a cloud based AWS emulator, instead of just using a real AWS account.