Thanks a lot, but do you have idea that you haven't mentioned the previous videos for this section that one should refer to as I came directly to this video and I have no idea where shall I manage previous steps for session, hence unable to follow-up
@@holodeck_run Thanks Ryan. Anyway I found all these videos and binged watched and learned so much from all these. Frankly speaking, you quick videos taught me so much that I haven't learned from hour long videos of others.
Why the hell my production level server would restart daily or crash? What a stupid thing to say. User session on frontend changes frequently but backend server should stay as stable as it can.
Your server might be free from crash-inducing error paths but your hosting provider might still restart your server for you. Many hosting providers tell you to treat your servers as completely stateless and ephemeral since they may need to do any number of things in the underlying architecture without you knowing. A good example is Heroku: they automatically restart all their servers daily and you can't do anything to shut that off. It's part of a wider trend in web servers/deployment architectures. Best to think of servers as something that come and go and not keep any state there.
@@jj.alex0616 sessions should be persisted with some kind of key-value store like Redis or something similar. Since that service will run independently of your backend, a server restart for your app server won't affect sessions. This is how it's done with most session-based auth services.
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
this course looks very high quality, will check it out. thank you for actually zooming in so i can see the code side by side on my small laptop :)
Amazing tutorial 😍
So helpful. Thank you 💙
Thanks a lot, but do you have idea that you haven't mentioned the previous videos for this section that one should refer to as I came directly to this video and I have no idea where shall I manage previous steps for session, hence unable to follow-up
Hi! Thanks for the feedback. Here's the full playlist: ua-cam.com/play/PLlRapu2ErjJ-qSQT9fhh3wdgLU8nynzeN.html
@@holodeck_run Thanks Ryan. Anyway I found all these videos and binged watched and learned so much from all these. Frankly speaking, you quick videos taught me so much that I haven't learned from hour long videos of others.
@@contactdi8426 Glad to hear it!
Hi, For production how to use the session? Please help me. Thanks in advance.
I'd recommend something like Redis for persisting sessions in prod 👍
Can you help me set a session for an application
Thankeww for knowledge😊
Hi, Can you post the source code for this tutorial
Sure thing, here it is: github.com/chenkie/orbit
@@holodeck_run Thank you
Why the hell my production level server would restart daily or crash? What a stupid thing to say. User session on frontend changes frequently but backend server should stay as stable as it can.
Your server might be free from crash-inducing error paths but your hosting provider might still restart your server for you. Many hosting providers tell you to treat your servers as completely stateless and ephemeral since they may need to do any number of things in the underlying architecture without you knowing. A good example is Heroku: they automatically restart all their servers daily and you can't do anything to shut that off.
It's part of a wider trend in web servers/deployment architectures. Best to think of servers as something that come and go and not keep any state there.
@@holodeck_run how would we then have a session persist after a resetting your back-end server?
@@jj.alex0616 sessions should be persisted with some kind of key-value store like Redis or something similar. Since that service will run independently of your backend, a server restart for your app server won't affect sessions. This is how it's done with most session-based auth services.