Serverless Architecture based on a domain model?

I have recently started using serverless, I completed the tutorial on serverless-stack.com and I wanted to see if there was a way could represent the domain model in an application. I've searched for some samples but I can't seem to find anything.

I have an application that I would like to model. How would I reference this in the main serverless.yml file? How would I make them part of the same API gateway?

/users
serverless.yml
/posts
serverless.yml
/comments
serverless.yml

thanks in advance

• You're correct from a DDD and MSA perspective that Users, Posts and Comments are different micro services and thus should have their own serverless.yml. This implies one API Gateway for each. That's a good thing.
• It's probably a lot easier if they were in separate repos as well, for ease of CI/CD. You don't want a single commit to trigger deployment of 3 services.
• If you really do want a single API that aggregates Users, Posts and Comments, then perhaps a fourth API that acts as a facade to the other three would be best. It's an established design pattern in OO, SOA and MSA.