Stateless processes
This was called Processes in the original 12-factor principle and stated that an application's processes should be stateless and share nothing. Stateless processes here means that a single process should not expect to retain any state information, whether it is on a container's disk or its memory, since there is no guarantee that information will be retained. Should state need to be retained, it should be done so externally to the application through backing services, such as Redis. Share nothing processes relate to when more than one process runs concurrently in the container. A good practice would be to avoid sharing and storing state between these processes; this makes the application less complex and easier to maintain. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access