Live data from Hacker News

Localstack – Local AWS Emulator

github.com

131–132 of 132 posts

Re: Localstack – Local AWS Emulator

#131

Earlier quoted context omitted.

I legitimately wonder how many people feel free from lock in after they finish paying $75k to Canonical for a 12 node OpenStack "private cloud build" ( https://assets.ubuntu.com/v1/d4766546-Private-Cloud-Build_Da... ), not to mention ongoing support bills and billing for addons "starting at $25k". Just because something is open source does not mean your org will actually have the expertise to be successful at running…

> I legitimately wonder how many people feel free from lock in after they finish paying $75k to Canonical for a 12 node OpenStack "private cloud build" Here’s the part where it’s not lock-in. We stopped paying for support from Redhat when we got big enough that our own SRE expertise to run our own open stack cloud. You know what the impact was on our applications running on it? Absolutely nothing. How much do you pay…

Even if it doesn't cost you in monthly payments to a tech company it still costs you in "our own SRE expertise to run our own open stack cloud" so salaries, benefits, 401k contributions, etc.

> I can’t wait until 20 years from now when all of the proprietary shit looks ridiculous in hindsight.

I'd posit that in 20 years there will still be tech which is more efficiently managed by a central provider, rather than having each company hiring their own independent expertise.

Re: Localstack – Local AWS Emulator

#132
post #86

It's impressive what Localstack has been able to do to keep up with AWS. However for my own projects, we consider local development like this an anti-pattern. IaC tools like Terraform/CDK/SST make it easy to spin up environments for each developer in the cloud. This may sound crazy at first but would recommend giving it a shot. If you're fully taking advantage of managed AWS services the best development environment…

It’s not really that impressive all things considered. Localstack is effectively Python’s Boto library (an AWS mocking tool) running as a server.

In turn, all of the AWS APIs are defined by a kind of JSON schema document, so there’s not really any reverse engineering going on.

I consider Localstack somewhat toxic in most projects because it shows the the developer didn’t understand how to contract test.

Furthermore, doing anything more than contract testing with AWS is a fool’s errand. The problem you face with Localstack is that it gives you an inaccurate model of how AWS actually works. As a general rule, AWS APIs are asynchronous, as in their side effects are not atomically bound to the request you’re making (sans some certain S3 actions); while Localstack is invariably synchronous.

Post reply on HN