serverless-esbuild VS elasticmq

Support Yarn PnP with externals bundling #327

We use serverless-esbuild to transpile our TypeScript code to JavaScript.

You should use appropriate tools to bundle your Lambda functions with a minimal size. For example, the Serverless Framework, with the serverless-esbuild plugin, automatically bundles your code and uploads it to AWS.

One of the most important aspects of serverless development is keeping an eye on your bundle sizes and to reduce cold start times on Lambda. Keeping this in mind, the template utilizes serverless-esbuild and serverless-analyze-bundle-plugin to provide function analysis out-of-the-box. I opted for serverless-esbuild over serverless-bundle for a few reasons:

Its faster and easier to setup that webpack and drastically reduces the size of the archive. For Serverless framework users there is https://github.com/floydspace/serverless-esbuild and if you use SAM CLI, you already get this for free since they now use esbuild in the build process

if you can, try using https://github.com/floydspace/serverless-esbuild - esbuild is stupid fast and it produces tiny artifacts. Its dead simple too compared to the webpacks/rollups/etc.

Since a majority of services rely on the same system services, we can leverage Docker to start all the needed project services prior running services with the offline command. The template ships with a base docker-compose.yml that stands up an instance of ElasticMQ to emulate Amazon SQS's API. The Docker image can be extended to include other services like DynamoDB, Redis, or PostgresQL and can be run using yarn infrastructure:build or yarn infrastructure:start depending on if it's your first run or not.

however...we have banned use of SQS. unlike S3/Minio, there's nothing API-compatible that we can run offline. (well, there's one thing, but it's in-memory / single node only and doesn't give us the durability/reliability we want with SQS). instead we use RabbitMQ because it's identical at the API layer no matter where we are. AWS has a hosted option for this but we haven't switched to it, because our existing self-managed Rabbit clusters are stable and well-understood.