serverless-localstack VS eucalyptus

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

They rebranded: https://github.com/corymbia/eucalyptus#readme but development is either happening "offline" or they've stalled development because https://github.com/Corymbia/eucalyptus-blog/blob/master/cont... is the most recent blog update

It's also a beast to even compile and package, to say nothing of actually deploy

The website is still up and points to a fork on GitHub:

- https://docs.eucalyptus.cloud/eucalyptus/5/install_guide/int...

- https://github.com/corymbia/eucalyptus/

There are quite a few moving parts. I think I got stuck around just comprehending the networking bits.