Your own local copy of AWS w/ Node.js

Getting started with LocalStack

Flo Sloot
6 min readFeb 1, 2019

Hint: There’s even a bonus at the end 🤫

No matter whether you’re a backend or frontend dev, most likely you have already interacted with AWS and/or services deployed to the same.

There are barely any companies that I have work with/for that don’t have infrastructure on AWS (or any other Cloud Provider).

Often these systems are a lot more complex than just an application running on an EC2 Instance.
A quite common architecture is to have multiple services in a microservice-based application that communicate over message queues.
On AWS the service that provides such a message queue is called SQS.
In production systems you’ll probably find SQS working hand in hand with SNS (simple notification service).
This type of architecture works pretty well (depending on the use-case of course) and scales great as f****.

Caveat

But neither is setting up such a system trivial and nor is developing against cloud servers.
Things can get costly. Things can get ugly when trying to access resources deployed in a VPC. But first and foremost things can get quite tedious when switching from local development environment to production environment.

--

--