> Your design goal should not be "create the smallest service you can to satisfy the 'micro' label".

A place I worked at years ago did what I effectively called "nano-services".

It was as if each API endpoint needed its own service. User registration, logging in, password reset, and user preference management were each their own microservice.

When I first saw the repo layout, I thought maybe they were just using a bunch of Lambdas that would sit behind an AWS API Gateway, but I quickly learned the horror as I investigated. To make it worse, they weren't using Kubernetes or any sort of containers for that matter. Each nanoservice was running on its own EC2 instance.

I swear the entire thing was designed by someone with AWS stock or something.