title: AWS K8S web application architecture choice
body: <p>I am trying to build a web application with Kubernetes and Amazon Web Service.
  I believe there are many different approaches but I would like to ask for your opinions!</p>
  <p>To make it simple, the app would be a simple web page that display information. User logs in, and based on filters, get specific information.</p>
  <p>My reflection is on the k8s inside architecture:</p>
  <ol>
  <li>Can I put my whole application as a Pod? That way, cluster and node scalability would make the app available for each user by allocating each of them 1 pod. Is that good practice?</li>
  <li>By following that logic, every different elements of my app would be a container. For instance, in a simple way, 1 container that contains the front of the app, 1 container that has the data access/management, 1 container for backend/auth etc</li>
  </ol>
  <p>So 1 user would &quot;consume&quot; 1 pod which containers' are discussing together to give the required data from the user. k8s would create a pod for every users, scaling up/down the nodes number etc...
  But then, except for the data itself, everything would be dockerized and stored on ECR (Elastic Container Registry) right? And so no need for any S3/EBS/EFS in my opinion.</p>
  <p>I am quite new at AWS and k8s, so please feel free to give honest opinions :) Feedback, good or bad, is always good to take.</p>
  <p>Thanks in advance!</p>