What can we expect from people who never tried / failed to understand how it works?

Whether something is dead or not is not up to you to decide. 'Reactive programming' and 'virtual threads' are tools, just like 'list' and 'set.' People should be familiar with these tools and choose the appropriate one depending on the problem. Good luck.

To avoid blocking the pipeline, you can utilize Mono or Flux without the need for virtual threads. Virtual threads, despite being less efficient, have vulnerabilities - if a user cancels a browser request, the virtual thread might not recognize the cancellation and could inefficiently continue fetching data. For optimal non-blocking functionality, Reactor is the preferred choice. Converting blocking code to asynchronous code can still incur costs. The individual who wrote this comment appears to imply a perceived limitation in your understanding of reactive programming. Virtual threads address the costliness of platform threads but do not inherently provide a non-blocking pipeline like reactor. Virtual threads efficiently utilize threads but lack the ability to cancel the pipeline, making Reactor still valuable.Of course you can use virtual threads in reactive pipelines. They have similar approaches but with the different use cases. Theoretically, adopting zero abstraction has the potential to surpass the current benchmark in terms of speed for reactor. Improving reactive programming primarily involves enhancing memory management and abstraction. Transitioning to zero abstraction could potentially result in faster performance compared to the current benchmark. However, this approach might compromise code cleanliness and make maintenance more challenging. In any case, I'm happy with the current results from the reactor.

@@vinothselvaraj8005 People always choose what they are familiar with or easy to understand.

@@sadiulhakim7814 Yes, I agree with that.

github.com/vinsguru/google-voice-search FYI - It was done 6/7 years ago. so simply cloning the project might not work.

Thanks - github.com/vinsguru/vinsguru-blog-code-samples/tree/master/nats/nats-vs-rest

Grafana has released few newer versions since I uploaded this video. Even though the UI has changed, high level functionalities remain same. If you could see the data in some form like table, then you could create charts. You can ask your questions in stackoverflow with some screenshots where you are facing and you would help.In youtube with limited info, very difficult to clarify.

github.com/vinsguru/vinsguru-blog-code-samples/tree/master/nats/nats-vs-rest

We should be able. But I never tried.

It is a plugin which you need to install

www.vinsguru.com/selenium-webdriver-managing-selenium-grid-infrastructure-using-arquillian-cube/

Zalenium seems to have been deprecated. I have a separate video on the usage of docker in test automation. Please check.

@@vinothselvaraj8005 but I basically want to know why docker instead of sause lab ?

Sauce lab is something like a paid remote grid service (they do have other features). They offer various browser/OS combos for your test automation. People use these services because setting up and managing such infrastructure is difficult and time consuming. Docker simplifies this by creating an on demand selenium grid. However docker can not provide various chrome/firefox with different OS combo. In my experience, I hardly see such browser issues with specific to an OS. So, I mostly go with docker.

www.testautomationguru.com/selenium-webdriver-real-time-test-execution-results-using-elasticsearch-kibana/

Sorry for the late reply. Grafana provides real time results with stunning charts. You can do a lot of customization

Check here - www.testautomationguru.com/embedding-zalenium-live-execution-in-jenkins/

Check this - www.testautomationguru.com/selenium-docker-integration-through-jenkinsfile-part-3-executing-tests-inside-docker-container/

:) I did not want but I had to.