3 ms·

Hey all - LocalStack co-founder here. Great to see this article trending. :) Happy for any additional suggestions and questions you may have. Looking forward t

Hey all - LocalStack co-founder here. Great to see this article trending. :) Happy for any additional suggestions and questions you may have. Looking forward to getting your feedback!

hw8kw13 5y ago
How would you differentiate yourself from a tool like Moto, in terms of testing? https://github.com/spulec/moto https://github.com/spulec/moto
- whummer 5y ago
  Great question - we're working very closely with moto, in fact our team very actively contributes to the moto core on a regular basis. The main differentiator is that moto is a Python library that mocks out / implements the AWS APIs, whereas we see LocalStack as a platform that aims to support the end-to-end development lifecycle for your cloud apps. A lot of the work we do in LocalStack is to create a seamless dev experience in your local environment - providing local DNS integrations, persistence features, Lambda code mounting, CI integrations, transparent injection of "localhost" endpoints into AWS SDKs (e.g., for your Lambda functions), and much more. Also, today we already provide some fairly sophisticated integrations - e.g., our Athena API which allows you to run your SQL-like big data queries natively over the local S3 filesystem. This is out of scope for moto, but a big focus area for us. Our aspiration is that you can take any (AWS) cloud app and deploy it natively to LocalStack - which is already the case in many scenarios, and improving on a daily basis. Btw, we're currently working on revamping/polishing our docs with lots of more content and details - we'll push out an update to https://localstack.cloud/docs https://localstack.cloud/docs in the next couple of days!
DandyDev 5y ago
Localstack Pro looks quite nice and comprehensive, but the CI pricing seems to really discourage proper continuous integration best practices. At 10 cents per run you're encouraging developers to run their CI pipelines as little as possible, while ideally you'd run CI on each commit and you'd commit often, probably 10s is times a day. In that case Localstack Pro for CI would get costly very quickly. Why not have CI pricing per project/repo. Regardless of how often it runs.
- whummer 5y ago
  Thanks for the feedback, great points. We're going to put a strong focus on our CI offering (both from a feature and pricing point of view) over the next couple of weeks/months. For example, we're working on a new feature that will make it easy to snapshot the state of the LocalStack instance during and after each CI run, making the state "browsable" in the UI, and providing advanced insights and analytics into how the application stack and tests evolved over time. We're also looking into alternative options for pricing - your point is well taken and will be considered for our roadmap. We definitely want to encourage testing frequently and on every commit - but I'd like to emphasize that our current CI offering is just a starting point, with lots more exciting features to come soon.. Thanks!
- hansel_der 5y ago
  how did that 'mining coins on gh-actions' thing turned out again?

Hey all - LocalStack co-founder here. Great to see this article trending. :) Happy for any additional suggestions and questions you may have. Looking forward to getting your feedback!

hw8kw13 5y ago

How would you differentiate yourself from a tool like Moto, in terms of testing? https://github.com/spulec/moto https://github.com/spulec/moto

whummer 5y ago
Great question - we're working very closely with moto, in fact our team very actively contributes to the moto core on a regular basis. The main differentiator is that moto is a Python library that mocks out / implements the AWS APIs, whereas we see LocalStack as a platform that aims to support the end-to-end development lifecycle for your cloud apps. A lot of the work we do in LocalStack is to create a seamless dev experience in your local environment - providing local DNS integrations, persistence features, Lambda code mounting, CI integrations, transparent injection of "localhost" endpoints into AWS SDKs (e.g., for your Lambda functions), and much more. Also, today we already provide some fairly sophisticated integrations - e.g., our Athena API which allows you to run your SQL-like big data queries natively over the local S3 filesystem. This is out of scope for moto, but a big focus area for us. Our aspiration is that you can take any (AWS) cloud app and deploy it natively to LocalStack - which is already the case in many scenarios, and improving on a daily basis. Btw, we're currently working on revamping/polishing our docs with lots of more content and details - we'll push out an update to https://localstack.cloud/docs https://localstack.cloud/docs in the next couple of days!

DandyDev 5y ago

Localstack Pro looks quite nice and comprehensive, but the CI pricing seems to really discourage proper continuous integration best practices. At 10 cents per run you're encouraging developers to run their CI pipelines as little as possible, while ideally you'd run CI on each commit and you'd commit often, probably 10s is times a day. In that case Localstack Pro for CI would get costly very quickly. Why not have CI pricing per project/repo. Regardless of how often it runs.

whummer 5y ago
Thanks for the feedback, great points. We're going to put a strong focus on our CI offering (both from a feature and pricing point of view) over the next couple of weeks/months. For example, we're working on a new feature that will make it easy to snapshot the state of the LocalStack instance during and after each CI run, making the state "browsable" in the UI, and providing advanced insights and analytics into how the application stack and tests evolved over time. We're also looking into alternative options for pricing - your point is well taken and will be considered for our roadmap. We definitely want to encourage testing frequently and on every commit - but I'd like to emphasize that our current CI offering is just a starting point, with lots more exciting features to come soon.. Thanks!
hansel_der 5y ago
how did that 'mining coins on gh-actions' thing turned out again?