Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
Great point. Fully agree that providing a first-class local development experience is critical to the overall story of application development frameworks.
I guess the main difference is that frameworks like Serverless provide a great experience if you fully buy into their way of doing things (i.e., implement your application assets in the Serverless YAML DSL, etc), whereas LocalStack is a generic platform that works on the API emulation level, hence integrates with most tooling out of the box.
Making the switch from Serverless to, say, AWS CDK, or AWS SAM, or Architect framwork may not be as seamless - however, for each of these frameworks you can always run the local emulation natively on LocalStack. This can help reduce the overall vendor lock-in effect that a lot of application development frameworks come with.
In fact, LocalStack also provides an integration with Serverless [0] - among many other tools [1].
[0] https://github.com/localstack/serverless-localstack
This is really impressive.
I've been running a scraper against the output of the "aws --help" CLI commands for a few months, to try and get a better feel for how often AWS changes - I call this "help scraping". The answer is it changes a LOT - there are updates to their APIs every single day.
Here's the commit log of changes I've tracked so far: https://github.com/simonw/help-scraper/commits/main/aws
Related posts
- Turbocharge your Lambda Functions with AWS Lambda Powertools for Python
- Optimizing Costs in the Cloud: Embracing a FinOps Mindset
- Billing for SaaS with EMF and CloudWatch Metric Streams
- Serverless Site Health Check Notification System
- Advice for unattended vending machine startup with basic api, crud, and database needs