Stateful vs Stateless Architectures Explained

[@hayk.simonyan]

Free System Design Course: skool.com/web-dev-mastery

[@lovingnation3223]

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.

[@hayk.simonyan]

Glad to hear that. Thanks from my editor as well :))

[@devkasunlakshitha]

Best explain about stateful/stateless architecture. Thank you!

[@lodosdurak7913]

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.

[@adityatripathi9125]

Exactly! I was thinking the same. Its clients responsibility to communicate state details with each requests.

[@sheikhAbdelrahman]

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).

[@hayk.simonyan]

You're right that both architectures can maintain state, but the key distinction is where and how the state is stored and managed. In case of stateless the server doesn't retain session information between requests and relies on external storage, but in case of stateful they handle state directly on the server. Hope that clears it up!

[@longgpham6396]

thank for calling out, I'm also confuse about "Stateless" here. For me, it is more like a technic or system design to scale horizontally at server level

[@JardelNovaes]

@@hayk.simonyan Server side is maintaining state on the server on both cases, it's not stateless. The "media" you store the session information on server side doesn't make it stateless. You point is about a "share storage" on server. @lodosdurak7913 gave us an example of stateless, when request need to send "all information" every time, since there is "no state" on the server (stateless)

[@Senboni]

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?

[@hayk.simonyan]

Absolutely! The shared database must also scale alongside growth. That's exactly what I discussed in a previous tutorial, so be sure to check out the video on database replication and sharding on this channel.

[@opethforlife]

Now I understand. Many thanks .

[@AllahomAnsorGaza]

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 ?

[@sumitgoyal8108]

legend finally understood

[@israelterorisprikopat]

Which situation need use Statefull?

[@hayk.simonyan]

when you need to maintain context or state across multiple requests or interactions

[@FelipeYonehara]

Multitenancy next.

[@galleon8129]

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

[@jaymartinez311]

I think you missed the point of the video 😂. It’s for beginners. Use your imagination.