4 ms·

Localstack: A fully functional local AWS cloud stack

86 points by lucis 7y ago

mchristen 7y ago
I use this project, but calling it 'fully functional' is quite a leap.
- simlevesque 7y ago
  which part do you use ? I'm thinking about asking my boss for a subscription, I want to test Greengrass.
  - mchristen 7y ago
    I use the S3, SQS and SNS extensions all the time. Absolutely fantastic during development and testing, even for small scale staging deployments sometimes.
jaequery 7y ago
How many times is this going to get posted on HN?
- o-__-o 7y ago
  Need more Pro buyers to fund the YC investment vehicle..
  - chews 7y ago
    You got my updoot.
Fripplebubby 7y ago
Just started using this last week. If you use terraform, it hooks in very nicely, too: https://www.terraform.io/docs/providers/aws/guides/custom-service-endpoints.html https://www.terraform.io/docs/providers/aws/guides/custom-se...
- anbotero 7y ago
  Wow, thanks for this wake-up call! I had checked localstack + Terraform combo some time ago and I don’t recall that option being there. Time to refresh my knowledge on this.
ssss11 7y ago
“ LocalStack provides an easy-to-use test/mocking framework for developing Cloud applications. Currently, the focus is primarily on supporting the AWS cloud stack.”
detaro 7y ago
duplicate: https://news.ycombinator.com/item?id=21436244 https://news.ycombinator.com/item?id=21436244
makstaks 7y ago
I started using Localstack and wanted to make it work, but found myself using a sandboxed AWS account more and more over time because there was less friction.
kapilvt 7y ago
sigh, i vaguely remember when local stack was free, back when it was moto (library + rest support), and then atlassian doing the initial localstack, and then handing it over to the community. on the day after docker is done, i'm not sure there's much vc value add in the pure dev tools space, its feeding into a commodity with a motivated community, especially in this case given a cost incentive (per dev licensing) and higher fidelity alternative in using an actual test account.
- kapilvt 7y ago
  fwiw, I tried local stack a while ago, and quickly realized that features and edge cases where not really where it worked. it hits the 80/20 rule of apis and a 20/80 rule on error conditions. I switched out to flight recording on the apis to get better coverage and tracking to new features and more customizable err injection. if this space is of interest, here's a five minute vid I did on testing in aws last year. https://www.youtube.com/watch?v=l-4qdyEm-YA https://www.youtube.com/watch?v=l-4qdyEm-YA
  - mpb88 7y ago
    Great video! Thanks for sharing. I have had a lot of trouble mocking my AWS calls. I’m going to give flight recording a try because I am already basically doing that in my mocks, but manually. It’s painful.
  - solipsism 7y ago
    It's amazing to me that a video like this is apparently sanctioned by two large companies, and yet the use of terminology is so very divergent from the norm. The thing you're calling "stubbing" (a usually local, working implementation of a subset of a service's functionality) is usually called using fakes. You describe Moto as a "stubbing" library, but it's neither a stubbing library nor a fake... it describes itself as a mocking library, and that's exactly what it is. You describe localstack as a stubbing library that combines "best of breed stubs"... but it's actually a collection of fakes built up from simpler fakes and mocks (their readme says "LocalStack builds on existing best-of-breed mocking/testing tools"). I don't know if you're purposefully using nonstandard terminology or if you're just mimicking how the terms are used inside Capital One, but since this video is educational, it seems irresponsible to diverge so far from industry-standard terms. Please read https://martinfowler.com/articles/mocksArentStubs.html https://martinfowler.com/articles/mocksArentStubs.html (particularly the The Difference Between Mocks and Stubs section) for a good description of how the terms are usually used. Note, I don't think it's very important which terms are chosen to mean which thing. But we need some consistency. The fact that you're disagreeing with the terminology that's used in the readmes of the tools you're talking about should be a clue.

86 points by lucis 7y ago

mchristen 7y ago

I use this project, but calling it 'fully functional' is quite a leap.

simlevesque 7y ago
which part do you use ? I'm thinking about asking my boss for a subscription, I want to test Greengrass.
- mchristen 7y ago
  I use the S3, SQS and SNS extensions all the time. Absolutely fantastic during development and testing, even for small scale staging deployments sometimes.

jaequery 7y ago

How many times is this going to get posted on HN?

o-__-o 7y ago
Need more Pro buyers to fund the YC investment vehicle..
- chews 7y ago
  You got my updoot.

Fripplebubby 7y ago

Just started using this last week. If you use terraform, it hooks in very nicely, too: https://www.terraform.io/docs/providers/aws/guides/custom-service-endpoints.html https://www.terraform.io/docs/providers/aws/guides/custom-se...

anbotero 7y ago
Wow, thanks for this wake-up call! I had checked localstack + Terraform combo some time ago and I don’t recall that option being there. Time to refresh my knowledge on this.

ssss11 7y ago

“ LocalStack provides an easy-to-use test/mocking framework for developing Cloud applications. Currently, the focus is primarily on supporting the AWS cloud stack.”

detaro 7y ago

duplicate: https://news.ycombinator.com/item?id=21436244 https://news.ycombinator.com/item?id=21436244

makstaks 7y ago

I started using Localstack and wanted to make it work, but found myself using a sandboxed AWS account more and more over time because there was less friction.

kapilvt 7y ago

sigh, i vaguely remember when local stack was free, back when it was moto (library + rest support), and then atlassian doing the initial localstack, and then handing it over to the community. on the day after docker is done, i'm not sure there's much vc value add in the pure dev tools space, its feeding into a commodity with a motivated community, especially in this case given a cost incentive (per dev licensing) and higher fidelity alternative in using an actual test account.

kapilvt 7y ago
fwiw, I tried local stack a while ago, and quickly realized that features and edge cases where not really where it worked. it hits the 80/20 rule of apis and a 20/80 rule on error conditions. I switched out to flight recording on the apis to get better coverage and tracking to new features and more customizable err injection. if this space is of interest, here's a five minute vid I did on testing in aws last year. https://www.youtube.com/watch?v=l-4qdyEm-YA https://www.youtube.com/watch?v=l-4qdyEm-YA
- mpb88 7y ago
  Great video! Thanks for sharing. I have had a lot of trouble mocking my AWS calls. I’m going to give flight recording a try because I am already basically doing that in my mocks, but manually. It’s painful.
- solipsism 7y ago
  It's amazing to me that a video like this is apparently sanctioned by two large companies, and yet the use of terminology is so very divergent from the norm. The thing you're calling "stubbing" (a usually local, working implementation of a subset of a service's functionality) is usually called using fakes. You describe Moto as a "stubbing" library, but it's neither a stubbing library nor a fake... it describes itself as a mocking library, and that's exactly what it is. You describe localstack as a stubbing library that combines "best of breed stubs"... but it's actually a collection of fakes built up from simpler fakes and mocks (their readme says "LocalStack builds on existing best-of-breed mocking/testing tools"). I don't know if you're purposefully using nonstandard terminology or if you're just mimicking how the terms are used inside Capital One, but since this video is educational, it seems irresponsible to diverge so far from industry-standard terms. Please read https://martinfowler.com/articles/mocksArentStubs.html https://martinfowler.com/articles/mocksArentStubs.html (particularly the The Difference Between Mocks and Stubs section) for a good description of how the terms are usually used. Note, I don't think it's very important which terms are chosen to mean which thing. But we need some consistency. The fact that you're disagreeing with the terminology that's used in the readmes of the tools you're talking about should be a clue.