Great presentation! There is also http2 protocol which is binary by default and allows connection multiplexing - reusing a single connection for multiple http requests (including SSE streams)
This was an excellent presentation! I was fully engaged the entire time -- great work! Also, would love the slides posted somewhere (maybe even on your personal site)!
Amazing brother great and simple presentation . Keep you content more in English it's easy to understand i try to watch your other videos but every thing goes over from my head for language barrier. take love from Bangladesh
Hey Azim, your presentation was so good I checked out your channel but couldn't find much videos in English. I have still subscribed in the hope that you'll someday post more in English!! :D
38:32 Sure, for simpler use cases you can use SSE. But generally what happens is, the server has data for thousands of stocks, but a client only needs data for one or a handful of stocks which can also be dynamically updated. So websockets help in this case to get the message from the client for which stocks they want to subscribe/unsubscribe e.g. unsub from AAPL, sub to MSFT, etc
I loved every minute of the video , I'm learning back-end using django/flask , i did some projects in both , do you think learning Go is a good addition to my resume ?
Great Talk ! What are the ways to make Event Stream more robust. For example, when BE is streaming events, suddenly FE crashes, and BE also loses the state. Probably, we can work out things with request-ids, but any other ways so that if FE is closed, events are not streamed but saved somewhere, and queued itself for the retry and etc.
event stream is already pretty robust (has retry logic in client side). In case of client crash, reloading the page should receive most current data via API and depend on SSE only for receiving updates. Client might miss messages e.g. they are offline. When they're back online it should receive all or current state and subscribe to receive future updates via SSE.
Not sure if i understand correctly, real time mean bound in time, however all this presentation seems about application being fast and not bind by time, a realtime application/system is application that is bound in time.
In fact, there is a limit to the number of open connections, at least on Linux. On Linux, everything is a file, so you need to plan for the maximum number of open file descriptors.
Streaming response can be achived in any framework, because it's http feature. Not sure about having more control. Java will do as well, but you can expect around 10 times more (or even more) required memory same program. Not mentioning that you have to learn bloated framework first to even get started, because there is no prod ready build-in http server.
If I want to build something I have never known how to build it I couldn't help but ask AI how to build it without code and sometimes with code . And I still don't know how to really build it at all if I don't ask AI at all. I would like to ask how do I start and improve how to think about how should I build things (which steps should be included)? Eg I want to cook spaghetti I know what the ingredients are so I can cook but in code I don't know what the ingredients are so I don't know how to improve it at all.
would be cool to see something like this without absolutely unnecessary stuff like gorilla or other 3rd party stuff that can be trivially done with go std lib
Well presented with clear examples and excellent audience engagement! Great job!
What a presentation. Was blown away. Simple, engaging style. Thanks a lot Azim bro. You're special
Brother this is one, if not the best lecture I've seen online in recent years. So clean and elegant. Great job 😎
Great presentation! There is also http2 protocol which is binary by default and allows connection multiplexing - reusing a single connection for multiple http requests (including SSE streams)
Amazing presentation. I'm impressed, I'm learning network programming and the way he explained everything was so simple and easy to understand.
This was an excellent presentation! I was fully engaged the entire time -- great work! Also, would love the slides posted somewhere (maybe even on your personal site)!
Amazing brother great and simple presentation . Keep you content more in English it's easy to understand i try to watch your other videos but every thing goes over from my head for language barrier. take love from Bangladesh
Hey Azim, your presentation was so good I checked out your channel but couldn't find much videos in English. I have still subscribed in the hope that you'll someday post more in English!! :D
That's perfect presented, My english is not perfect but all of above I understand it. Thanks Azim Pulat
38:32 Sure, for simpler use cases you can use SSE. But generally what happens is, the server has data for thousands of stocks, but a client only needs data for one or a handful of stocks which can also be dynamically updated. So websockets help in this case to get the message from the client for which stocks they want to subscribe/unsubscribe e.g. unsub from AAPL, sub to MSFT, etc
simple and clear prensentation, great job!
wow, amazing, I just started to learning go, then i found your video, it's motivated me a lot.
This is a great gist. I'm getting much more in love with Go. Thanks for sharing.
Great presentation! Clear explanation and easy to understand. Practical examples. Learn a lot in Q&A 👍
I hope u can make more go tutorial. Your english very clear. I love it. I can listen without stop
Amazing work and presentation, Azim :)
I proud with you, I am uzbek and you show us how we can change world if we want this I wish every people reach their own goals
I'm Ukrainian, but Uzbeks are super humans!
@@winfle Thanks bro
Shunchaki faxrisiz O'zbekistonning, Alloh bardavom qilsin
really nice presentation, learnt some things from here for sure! thank you a lot.
He's explained it very well. Expecting more content like this.
That's sick. Love Go. So simple
Thanks, This was such an amazing talk!!
Nice presentation! Thanks for the upload.
was great presentation also enjoyed the jokes to big thanks from Morocco
Amazing job Azim, thanks for sharing & keep going ✌🏽
Amazing presentation, whole lotta new things I need to explore. thanks 👍
We are proud of you 🇺🇿🇺🇿🇺🇿🇺🇿
I don't know which country it is but I'm proud of him too 🎉
@StingSting844 Uzbekistan 🇺🇿
Can I access the power point presentation please?
Just fascinating. Keep it up:)
Hi, thanks for the presentation, but we need the screen of slide larger and presenter smaller
This is awesome! Your presentation was top notch!
Really great job answering all those questions fired at you
I am not a Go developer, and now I know Go thanks to you
Loved it G!!
Very good talk. Thank you very much
Greetings Azim, When you said event-based I/O at 35:58 were you talking about kqueue or epoll?
I loved every minute of the video , I'm learning back-end using django/flask , i did some projects in both , do you think learning Go is a good addition to my resume ?
Thanks for these presentation.
this is a good presentation
Nice presentation, thank you so much.
Your intro where you speak about who you are and where you work is clever lol
No it's you who's dumb
Thanks for sharing Azim, you're great!
love the presentation!
Great job!
Great presentation!
Great Talk !
What are the ways to make Event Stream more robust. For example, when BE is streaming events, suddenly FE crashes, and BE also loses the state. Probably, we can work out things with request-ids, but any other ways so that if FE is closed, events are not streamed but saved somewhere, and queued itself for the retry and etc.
event stream is already pretty robust (has retry logic in client side).
In case of client crash, reloading the page should receive most current data via API and depend on SSE only for receiving updates. Client might miss messages e.g. they are offline. When they're back online it should receive all or current state and subscribe to receive future updates via SSE.
Not sure if i understand correctly, real time mean bound in time, however all this presentation seems about application being fast and not bind by time, a realtime application/system is application that is bound in time.
In fact, there is a limit to the number of open connections, at least on Linux. On Linux, everything is a file, so you need to plan for the maximum number of open file descriptors.
any books do you recommend for learning go and be a pro in it ?
Thank you for share this with us
Great! With adding tiny bit of htmx even better 😊
great video. but this is a tech talk so please focus on the screen instead of the speaker. i cannot see too tiny letters.
awesome talk 🎉
yo you are too good at speech
You don't need a description bro is the description. Really Appreciate for this amazing session. Thanks a lot :)
The way you explain small things🎉 you should make go course maybe concurrency
wonderful
Great thanks for sharing
I'm not a programmer, but this lecture was interesting for me too🙃
Thanks for prensentation
The best
Thanks for meeting 🤝
Great job man❤
good presentation, thankyou. i want to ask how about grpc?
Well done 👍
gap yuq) zur video)
Coolest introduction. Can I steal it?
Top presentation
It is great!!!
Great
What about gun js that use peer to peer protocol? Is really peer to peer?
It's cool bro
Good job man!
comparing to mqtt. how do u think ? if both benchmarking
For Another thing you can use SSE is showing realtime Progressbar ( Messages )
great talks
thanks so much, it helps me alot
We can achieve Streaming response even with Java reactive programming with more control
Streaming response can be achived in any framework, because it's http feature. Not sure about having more control. Java will do as well, but you can expect around 10 times more (or even more) required memory same program. Not mentioning that you have to learn bloated framework first to even get started, because there is no prod ready build-in http server.
Amazing
Do you want to share a presentation link?
I got hooked
Cool❤
Do more english go videos please!
Please bring more
If I want to build something I have never known how to build it I couldn't help but ask AI how to build it without code and sometimes with code . And I still don't know how to really build it at all if I don't ask AI at all. I would like to ask how do I start and improve how to think about how should I build things (which steps should be included)? Eg I want to cook spaghetti I know what the ingredients are so I can cook but in code I don't know what the ingredients are so I don't know how to improve it at all.
great
is there any git repo for the meme generator backend app?
thanks for the presentation, you did a great job!
Thank you
thank you
#golang
we cant see the code on screen
bro you are like from my country aren`t you from Uzbekistan bro ?
Can you come to Dev fest Kigali 2025 please
🙋♂️
👍👍
💯👍
gonna to switch to golang from java))))
would be cool to see something like this without absolutely unnecessary stuff like gorilla or other 3rd party stuff that can be trivially done with go std lib
Nice F5😂