how to structurize AWS Serverless application?

Question

我发现 nano services 看起来适合 AWS lambdas 的架构是真的，还是我应该坚持使用经典的微服务架构？

Answer 1

AWS lambda's are not a complete architecture, they are merely a component.

The functionality you described in your comment would need a full-stack solution, because you need to manage state, etc. Classic microservices sounds like a safer approach because:

• It's a more well understood architecture, so there will be more resources you can leverage. At this stage, from the little reading I have done, nano seems a bit "flavor of the month".
• Microservices are much closer to providing a full stack, where as AWS lambdas are only part of it. With a microservices architecture you'll be more consciously considering a wider range of technical aspects.

If you decide to take the lamdba approach You'll have "nano" architecture based on lambdas, and everything else. Not sure how good an architecture that will be - because it won't be "balanced" if you put all your focus on the lambdas. Architecture needs to be holistic, if you are too preoccupied with lambdas you will miss other important things, or and try and use lambdas where a different approach would have been better.