04 Async in server side apps (Reactive programming with Java - full course)

preview_player
Показать описание
Course: Reactive programming in Java
Covers: Reactive fundamentals, Project Reactor

Access this full course NOW & unlock more awesome courses like this by becoming a member:

Website:

Learn the basics of reactive programming. You will learn to "THINK REACTIVE" - understand the paradigm shift and thinking change necessary to write code in a reactive way using Project Reactor.

New video every 3 days! Subscribe and enable notifications to be alerted.
Рекомендации по теме
Комментарии
Автор

Sir.. only teacher who don't assume the student knows it all.. and always give foundation before concepts.. no big words.. but simple meaning of things.. thank you sir.. big respect

kabyasingh
Автор

Best Java teacher in the world I have ever came across

karthik.karunanithi
Автор

I can not express myself how I am glad for Your hard work for us. Thank!!!

jozefs.
Автор

Great explanation.

If we want to make it truly async, remove the join, and make the return type of the controller as CompletableFuture<User> and return the callback of the combined futures

ankitsharma
Автор

We can return CompletableFuture<User> from the controller method and we could have used thenCombine method of completableFuture to avoid join() call.. In that way, we could have achieved async. And we can handle errors gracefully using ControllerAdvice in spring. Really excited and looking for reasons why reactive programming is a big thing now and how it provides better features than using completableFutures API

paragkanodia
Автор

Done thanks!
Handling a request that makes two calls to db then returns a User.
Doing two blocking operations sequentially and returning an object is inefficient because we block on the first call then block again for the second, we can speed this up by making the blocking calls asynchronously in parallel (by submitting them to a threadpool or using CompletableFuture) but we still have to wait for both operations to finish before we can return. So implementing scatter gather pattern does not remove blocking on IO in your code, because to gather you have to wait for the operations to complete. This is where reactive programming can be useful. However, the framework itself has to support it, so that our return type can be a reactive type instead of User object.

mostinho
Автор

You explanation is amazing ! Just love the way you give the context and explain why exactly things are done in a particular way....great depth!

manojraghavan
Автор

I love the way you explained in simple terms

pinakapanilokam
Автор

What a cliffhanger! I can't wait to see the reactive version of this.

alanmangroo
Автор

The same question I had when I was trying to understand from some other channel, thanks a ton for it Kaushik Sir, was looking for it

shubhammahindru
Автор

I love this lesson! I love the way you explain complex things in an accessible language. Thank you and big respect!

mariyarussakova
Автор

thanks for sharing in such a great way . koushik I've observed one confusion at @ 7:20 why need to join() again separately when we have bothFutures as combined and joined already .I think might be forgot to remove 😀

waqasrana
Автор

Hello Sir. Love this course. I completed it on your website. I have all access pass for 6mo. Thank you

kbgagt
Автор

I totally agree with you sir, i have't used it yet. But based in the clean explanation and having knowbledge of the model. The price to pay is considerable high, probably in exceptional cases where you really know the the timings of licycle events of what you are trying to make async.

minor
Автор

Now I understand why java needs reactive programming. Thank you.

wjhuang
Автор

Very much looking forward for the rest of the course..Thank you !

ramkethireddy
Автор

Sir, with all due respect, I really adore your teachings and simplistic explanation of concepts, but it is not always that as a developer or architect we do not think of quality, performance or security but the reality is the system also does not sometimes support us to deliver with quality because quality is also proportional to time with the unknowns that is there in software engineering and many a times, IMO or IME, system behaves as a feature factory

indranilchakraborty
Автор

I love this course. And also when you're launching the servlet programming course essentials? Looking forward to that 😀.

jessepinkman
Автор

I wish you could get Noble Prize for your teaching(If teaching is available as an category)

chandupurna
Автор

thanks a lot for this incredible course

erikbustos