Stateful vs Stateless Architectures Explained

СПАСИБО

I think there is a misconception here.
Both architectures are basically Stateful. The only difference is the storage of the state on a shared media or cache (ex. Redis).

since stateless is more scalable, you can add more servers -- easy. but what about the shared instance? in this case a database, it also needs to scale? how?

Which situation need use Statefull?

Stateless is when waiter leaves the order paper with the customer, so customer hands in the the order paper each time and updates accoridngly so the kitchen doesn't need to save the order info, its stored by the customer.

wtf is this, terrible explanation

Nice, but use real use cases from Azure or AWS. Elastic Beanstalk would be a good example

Now I understand. Many thanks .

Multitenancy next.

I am in IT for over. a decade and so far no one explained concept this better yet .. Excellent job! I think some credit goes to your video editor as she/he is spot on with with your script .. keep it up.

legend finally understood

the question is
in stateless server we need to query database for everything
and this consume time
while if there is array of current logged users
and if there is like websocket also so which is better ?

Best explain about stateful/stateless architecture. Thank you!

In a stateful architecture, the session ID can be stored on a centralized server, such as a session store. This setup allows any server in the system to fetch the session ID from the session store to process incoming requests. As a result, it eliminates the requirement for the same server to handle subsequent requests from the same client. In that case what is the disadvantage of stateful architecture. Please correct if my understanding is wrong.

loved it, you explain so good. god bless you.❤❤