Member-only story
A Microservice Architecture with NestJS & gRPC

Following on from my NestJS Pros and Cons article, I wanted to take a deeper dive into how NestJS can help you build a MicroService architecture out of the box. Microservice architectures are hugely popular and provide a lot of benefits to applications.
Microservices architecture (often shortened to microservices) refers to an architectural style for developing applications. Microservices allow a large application to be separated into smaller independent parts, with each part having its own realm of responsibility. To serve a single user request, a microservices-based application can call on many internal microservices to compose its response.
I just want to quickly touch on my personal pros and cons (although this isn’t a pro and con article). I’m fully aware that not everyone likes Microservice architectures and that’s fine.
Advantages
- Allows us to build, operate, and manage services independently, and we can easily scale them out based on the resources they need.
- Microservices take a lot of infrastructure risk out of the project straight away. With the infrastructure made almost invisible, microservice teams can iterate quickly.
- Each developer on a team can avoid getting tangled up in the underlying infrastructure, and focus on…