title: Structuring backend (REST API) into microservices with Kubernetes (or serverless)
body: <p>I'd like to design my next project in a microservices-based architecture rather than as a monolith. Are microservices generally defined as a set of endpoints that compromise a service (i.e. common dependencies, functionality, etc.) or would each endpoint be its own service? </p>
  
  <p>I've used <a href="https://serverless.com/" rel="nofollow noreferrer">Serverless Framework</a> before, which defines each endpoint with its dependencies and packages it into a Lambda/FaaS. In Kubernetes is this analogous to each endpoint living in its own pod?</p>
  
  <p>I'm having some trouble thinking about the ideal way to design a new project from the ground up that can make use of autoscaling, microservices, and pay-for-usage, and haven't found much information around it.</p>
  
  <p>Any thoughts/resources on this subject?</p>