christianfelicite
commented
4 years ago https://www.bizety.com/2018/08/21/stateful-vs-stateless-architecture-overview/
Stateless
- Stateless applications have just one function or service, such as an IoT device;
- They use web, print or CDN servers;
- The server processes requests based only on information relayed with each request and doesn’t rely on information from earlier requests – this means that the server doesn’t need to hold onto state information between requests;
- Different requests can be processed by different servers;
- The fact that any service instance can retrieve al application state necessary to execute a behavior from elsewhere enables resiliency, elasticity, and the ability for any available service instance to execute any task at all;
- Stateless applications are essentially containerized microservices apps;
- Orchestration for stateless apps helps determine the best location to run the container from the point of view of resources, including maintaining high availability (failover).
Stateful
- Stateful applications are typically databases;
- They involve transactions such as home banking;
- They use mail servers;
- The server processes requests based on the information relayed with each request and information stored from earlier requests – this means that the server must access and hold onto state information generated during the processing of the earlier request;
- The same server must be used to process all requests linked to the same state information, or the state information needs to be shared with all servers that need it;
- Orchestration for stateful applications involves determining the best location to run the container collection from the point of view of the applications’ overall needs including storage, network and IO Path point of view;
- Orchestration for stateful applications also manages high availability – moving containers and remounting volumes with no application or code changes.
https://fr.m.wikipedia.org/wiki/Serveur_sans_%C3%A9tat
Un serveur sans état est un serveur qui traite chaque requête de façon indépendante, sans relation avec les requêtes précédentes.
Il s'appuie sur un protocole sans état qui contient au minimum le format de la requête en entrée et le format de la réponse en sortie.
Les protocoles HTTP et IP sont des exemples de protocoles sans état.