遵循微服务的原则，
Defined domain: Each microservice has a defined domain of responsibility (sometimes referred to as a bounded context). The microservice manages this domain itself, without concerning itself about other domains.
Self-contained: Each microservice is a self-contained unit. It may contain multiple components that all work together.
Independently deployable: Each microservice can be built and deployed as an independent entity. Deploying one microservice does not affect another microservice.
Manages data stores: The data store or stores used by each microservice should be contained within the microservice boundary, thereby ensuring that there are no hidden dependencies caused by data stores being shared.
Loosely coupled: Microservices should be loosely coupled, and ideally communication will occur asynchronously using event sourcing or queues.
Highly automated: The build, deployment, and ongoing management of microservices should emphasize automation wherever possible.
我正在寻找代码结构/样板的建议，以实现这些原则，特别是独立部署、松散耦合和包含的数据存储。在AWS上使用无服务器框架。如果能参考工作良好的样板文件并实现这些原则，那么部署顺序就无关紧要了。
我偶然发现https://github.com/trilom/sls-microservice但这有makefiles。不喜欢不得不使用它们的想法。
我发现这正是正确的目的：https://github.com/zotoio/generator-mono-serverless