Spring Boot | Exploring Asynchronous 🚀 Calls with @Async Annotation | JavaTechie

#JavaTechie #SpringBoot #Asynchronous #Async #AsyncProgramming
👉 In this comprehensive video, we dive into the world of efficient Spring Boot development as we explore the power of asynchronous calls using the @Async annotation. Learn how to enhance performance and responsiveness in your applications effortlessly.
Spring boot microservice Premium course lunched with 70% off 🚀 🚀
Hurry-up & Register today itself!
COURSE LINK : javatechie5246.ongraphy.com/
PROMO CODE : JAVATECHIE50
OR use Javatechie APP
Download the JavaTechie app on your iOS or Android device from the App Store or Google Play Store.
Find the links below :
Android 🌐 :
play.google.com/store/apps/de...
IOS 🌐 :
apps.apple.com/in/app/javatec...
GitHub:
github.com/Java-Techie-jt/ord...
Blogs:
/ javatechie4u
Facebook:
/ javatechie
Join this channel to get access to perks:
kzbin.infojoin
🔔 Guys, if you like this video, please do subscribe now and press the bell icon to not miss any update from Java Techie.
Disclaimer/Policy:
📄 Note: All uploaded content in this channel is mine and it's not copied from any community, you are free to use source code from the above-mentioned GitHub account.

[@huseyinaydin1002]

I love javatechie and i love spring blood ❤😂

[@akhilanilkumar9090]

Adding bit more information @Async has two limitations: It must be applied to public methods only. Self-invocation - calling the async method from within the same class - won’t work. The reasons are simple: The method needs to be public so that it can be proxied. And self-invocation doesn’t work because it bypasses the proxy and calls the underlying method directly.

[@Javatechie]

Thank you akhil for clear update

[@__nitinkumar__]

@@Javatechie please make a video to cover these nuances of Async

[@RuslanZinovyev]

Spring uses a dynamic proxy pattern for all declarative operations such as @Async, @Transactional, @Cacheable, @Scheduled, @Retryable, @Validated etc.

[@uniquestreetfood8391]

@@Javatechie Hey Thank u for the video. But in ur video methods were called from same class. So how we achieved async here. Does it not contrast with above?Please help

[@Javatechie]

Yes even though it's from the same method it won't wait for a response to come back from the server rather it immediately gives a response to the end user .

[@johnabraham-mu3nv]

Good Explanation...Got clear clarity on Async concept.

[@RamKumar-dm6es]

You makes Java and Spring boot so simple. I love your content❤

[@ankurghosh4470]

thanks for making this video , this was really needed.

[@vinaykulkarni4085]

Good explanation. @Javatechie please create a detailed video on widely used caching techniques in Java with a real time example.

[@SumanaDey-lt2br]

Thank you so much for this video. Got better understanding.

[@dimalive132]

I like your practical approach of teaching stuff. I have learned a lot from your videos. Thank you very much.

[@veeravenkatasatyanarayanas136]

Thank you very much with quick walkthrough and understanding

[@theerans723]

Got a better understanding... keep going man !!

[@d.ramesh1224]

you make everything simple, great java techie

[@neethuk1294]

Thanks Java Techi :) love the way of explanation.

[@gopisambasivarao5282]

Appreciate your efforts @Basant. Nicely explained Spring boot @EnableAsync /@Async and ThreadPoolTaskExecutor concepts to achieve Spring boot Asynchronous calls. God bless you. 🙂🙏👍

[@saivignesh1758]

thanks for your video "it was soo easy to understand " , keep up the good work

[@debanwitadutta2303]

Very very good explanation..really appreciate your effort..currently for any unknown topics which I need to learn, I search for JavaTechie videos first..💗

[@user-od8cv2wo7u]

Simply Superb Explanation!!!

[@cmatthar]

That was a nice explanation and a very didactic example of how @Async works

[@umeshsharma2883]

Great explanation I got clarified on this.

[@yagnaa]

Bhai please create a end to end video on unit testing using mocito and junit5. btw love your content

[@Javatechie]

It's already there please filter in my channel you will get those videos

[@user-lw1dd4md5o]

Thanks brother for great explain you are great man 👌

[@chickpatilharshavardhan4806]

Thanks Sir Past 1week I am busy with Tenant-onboarding Automation in this there is serval methods to execute. But I will change my logic to @asyc call Thanks a lot🎉

[@theshivrajofficial8444]

Thanks for creating such awesome content.

[@kalamataway]

hi thanks for your video, would you consider using Spring events instead ? Would seem more suitable for me. Thanks in advance

[@psudhakarreddy6548]

Thank you brother 😊

[@rudrajitgupta3688]

Thanks Basant🎉🙌

[@prjvnd]

superb !!

[@maheshwaghmare2312]

Very good explanation

[@nehabajaj4002]

Nice explaination

[@itsnarahari]

Do a video on Junit test classes and Annotation, How to to test private, static methods

[@vitaliiseniuk5186]

Hi! Can you do OAuth2 AuthService + React as Client?

[@pro_gamer29569]

I have a question. I need to modify some large data and then return the response. Can i use asynchronous for this scenario or synchronous is better

[@rakeshranjan7388]

Hi Sir appreciate your effort, it was great tutorial, where I can get this code?

[@sudharshangowthu6871]

Explain the graphql concepts also.

[@ShubhamGupta-rn2ei]

Thank you for clear explanation sir......can you pls make a video of async calls with completables feature so that we can understand better for so many task execution at same time.

[@Javatechie]

Okay i will

[@ramangarg2684]

Please correct me if i am wrong- the order of execution cannot be predicted with the async logic. Can you please tell how to overcome this?wiuld CompletableFuture be a solution?

[@inhtruongvu7618]

🎯 Key Takeaways for quick navigation: 08:54 Nhằm *mục đích hoàn thành quá trình đặt hàng, tôi muốn thực hiện đồng bộ và các dịch vụ còn lại thực hiện bất đồng bộ* 09:22 Xem *hành vi mặc định của luồng làm việc khi chưa triển khai gọi bất đồng bộ* 10:19 Toàn *bộ luồng chính bị chặn để hoàn thành quy trình. Chưa triển khai gọi bất đồng bộ* 11:11 Toàn *bộ luồng được thực thi bởi một luồng chính duy nhất. Không phải thực hành tốt nếu có kịch bản phức tạp như vậy* 11:39 Làm *cho đặt hàng và thanh toán đồng bộ, các dịch vụ còn lại thực thi ngầm mà không chặn luồng chính* 12:05 Cần *tạo nhóm luồng riêng để không chặn luồng chính bằng cách thực thi trên một luồng đơn * 13:29 Cấu *hình kích thước nhóm luồng cốt lõi, dung lượng hàng đợi và kích thước nhóm tối đa* 15:04 Cấu *hình dựa trên số lượng lõi CPU của máy chủ * 15:58 Xác *định phương thức nào sẽ sử dụng cấu hình luồng tùy chỉnh để thực thi bất đồng bộ* 16:40 Đặt *hàng và thanh toán thực thi đồng bộ, các dịch vụ còn lại thực thi bất đồng bộ* 17:23 Phương *thức bất đồng bộ trả về void hoặc completable future* 18:04 Xác *minh luồng nào thực thi từng phần của luồng làm việc* 18:45 Chứng *minh ngay khi thanh toán hoàn tất, phản hồi được trả về mà không chặn luồng chính để thực thi toàn bộ luồng làm việc* 19:12 Khi *thanh toán hoàn tất, người dùng nhận được phản hồi ngay lập tức. Các quy trình khác thực thi bất đồng bộ với luồng khác * 19:51 Các *dịch vụ được thực thi trên các luồng khác nhau mà không chặn luồng chính* 20:19 Khi *thanh toán xong, phản hồi được trả về ngay lập tức. Các bước còn lại thực thi bất đồng bộ nền * 20:48 Triển *khai @Async cho phép thực hiện luồng làm việc bất đồng bộ trong microservice* 21:03 Ví *dụ sử dụng trình bày rõ ràng việc triển khai luồng bất đồng bộ với @Async* Made with HARPA AI

[@Briefseverus]

Respect

[@sifulislam7062]

what will happen if i create two or more executor ?

[@jessiejane6259]

For Async using spring-boot-starter-webflux is much better with the Mono data structures.

[@Javatechie]

If my application is non reactive then ?

[@prajyotlawande193]

What is the criteria to determine values for corePoolSize, maxPoolSize and queue capacity? I just can’t put any random nos. over there right? 14:00

[@Javatechie]

Correct we can't keep a random number Determining ThreadPoolExecutor parameters, such as queue capacity, core size, and pool size for `@Async` methods, involves considering various factors related to your application's characteristics and requirements: 1. **Task Duration:** If tasks are short-lived, a smaller core pool size and queue capacity may be appropriate to avoid unnecessary thread creation. For longer tasks, a larger pool and queue may help manage the workload. 2. **Concurrency Requirements:** Consider the desired level of concurrency. Adjust the core pool size accordingly to balance resource utilization with the need for parallelism. 3. **System Resources:** Be mindful of the available system resources, especially CPU and memory. Ensure that the configured pool size aligns with the system's capacity to handle concurrent threads. 4. **Queue Capacity:** The queue acts as a buffer between the producer (tasks submitting for execution) and the consumer (thread pool). A larger queue can help handle bursts of tasks and smooth out variations in workload. 5. **Throughput and Latency Goals:** Determine the trade-off between throughput and latency. A larger pool and queue may improve throughput but might increase the latency of task execution. 6. **Task Dependencies:** If tasks have dependencies or order constraints, a smaller queue or customized executor configurations may be needed to maintain the desired order of execution. 7. **System Load:** Consider the overall system load. During periods of high load, you might want to adjust the pool size to avoid overloading the system. 8. **Monitoring and Adaptability:** Regularly monitor the application's performance in real-world scenarios. If the workload patterns change, be prepared to adapt the thread pool parameters dynamically. 9. **Thread Starvation Risk:** Be cautious about setting the core pool size too low, as it may lead to thread starvation and impact the responsiveness of your application. 10. **Testing and Profiling:** Experiment with different configurations and use profiling tools to identify the optimal settings for your specific use case. This can help uncover potential bottlenecks and areas for improvement. Keep in mind that there is no one-size-fits-all solution, and the optimal configuration may vary based on the nature of your tasks and the specific requirements of your application. It's often beneficial to iteratively adjust these parameters and observe their impact on performance.

[@hamednikbakht9708]

hi, in big project use completable future or @Async and which one better please create video for completable future. thank you

[@Javatechie]

Both are used for different use case

[@karthikeyanrm3446]

Plesee continue the Java spring Microservices interview series with more complex questions..

[@SumitKumar-ec9nl]

Hello Sir Need to understand how flow will work with completable future , Please make a follow up videos or provide video link if already explained

[@Javatechie]

Good suggestion 🙂. I will

[@MarkMorales-du1nh]

I also want to see this. looking forward for this!

[@SumitKumar-ec9nl]

I am also waiting

[@sandeepravu]

Hi response to ClientA using api1. To summarize the flow: 1. **ClientA to ClientB (api1):** - ClientA initiates a request to ClientB using api1. 2. **ClientB to ClientC (apic):** - ClientB forwards the request from ClientA to ClientC using apic. - The forwarded request includes a callback URL (callbackapi1 of ClientB) and a request ID for future communication. 3. **ClientC processes the request:** - ClientC receives the request from ClientB. - ClientC sends an acknowledgment (ACK) to ClientA. - ClientC extracts the callback URL (callbackapi1 of ClientB) and the request ID from the request body. 4. **ClientC to callbackapi1 of ClientB:** - ClientC sends a response to the callbackapi1 of ClientB using the extracted callback URL (callbackapi1 of ClientB) and the request ID. - The response includes necessary information, such as the request ID and data. 5. **ClientB callbackapi1:** - ClientB processes the response from ClientC received through callbackapi1 (callbackapi1 API of ClientB). - Updates the database performed based on the information received, typically using the request ID and data. 6. **ClientB responds to ClientA:** - ClientB api1 waits for the callbackapi1 update. - After completing the update, ClientB sends a response to ClientA using api1. How to do this senario in spring boot. My clientB can deploy multiple server can you please provide best solution

[@karthikbalaji383]

Will the configuration change if there are DB/grpc calls and are there chance of deadlocks?

[@Javatechie]

No.changes needed and I don't understand why there will be deadlock?

[@sumitkumar-xz2tv]

Hey Basant I have one question that I get success response in postman but what if any thread fails even after response success

[@shakib_04]

good question. following.

[@Javatechie]

See for example some of the services failed then at the same time order status will be updated in the database. Since the user already has the transaction I'd he can monitor his order status by just doing a get call

[@ifeoluwae-stvadebayocoven9990]

These executor properties can be configured inside application.properties file right?

[@Javatechie]

Yes that's good practice to keep those parameters inside properties file

[@kastasir]

Async returns success (order 200 OK code), but async background calls can fail later

[@yogeshchaudhari9971]

Good video.....i have one query...say there is a method1() which is annotated with @aync......method1() internally calls method2()...... method2() internally call methods3()...... In such scenario do we need to use @aync before method2 and method3 as well? Please answer.. thanks in advance

[@Javatechie]

Not required i believe but still i will cross verify and update you

[@yogeshchaudhari9971]

@@Javatechie thanks for reply...yaa bcos i have a scenario in my project where first method calling second method...second method calling third method....seems its not working asynchronously as only first method is annotated with @sync...... Please confirm if possible...i am trying too...thanks again

[@Javatechie]

@@yogeshchaudhari9971 okay what's your return type of method is it completablefuture ?

[@yogeshchaudhari9971]

@@Javatechie no return type is not completeablefuture.....say there are 3 methods...method1..calls method2...method2 calls method3....method1 and method2 are void and method3 returns a user defined POJO JobApplicationSubmitEvent......

[@Javatechie]

@yogeshchaudhari9971 no if you want it to execute in async mode then you must need to define either void or Completablefuture

[@Asingh42]

Can we use virtual threads to achieve the same? Does spring boot support it?

[@Javatechie]

Yes we can do that and spring boot support it

[@Asingh42]

@@Javatechie thank you ! Can you make a video on that ? Your videos are really helpful buddy

[@Javatechie]

Sure I will do that

[@Asingh42]

Got news today that spring boot 3.2 will support virtual threads along with jdk 21

[@satyanarayanbehera3691]

If any exceptions occurred in the asynchronous method then how can we show that in response ?

[@Javatechie]

No you can't do that as all asyn execute in a separate thread so only you can log the error handling and final response in db

[@the_rocker7786]

I have implemented this and one thing I observed is it didn't print logs written in method which is annotated with async and it's obvious because mai thread gets finished earlier. But is there any solution for this?

[@Javatechie]

It should print not sure let me check and update you

[@the_rocker7786]

In real time how asynchronous response will be mapped to the request for which this respons is?

[@Javatechie]

I believe you didn't understand the flow of execution. Could you please check that again and again it will answer your doubts

[@the_rocker7786]

@@Javatechie ok so we will be setting tracking ID and using that user can retrieve it

[@Javatechie]

@the_rocker7786 yes that's what the standard in distributed system

[@user-cz9wf2ps4z]

Hi Bro recently in interview i got question like String input="ab45cfd23" the expected output is ab54cfd32 doing using java8 can please make video realting to these questions

[@Javatechie]

I will shortly update you

[@user-cz9wf2ps4z]

i am waiting for ur response hope u will reply soon@@Javatechie

[@Javatechie]

@@user-cz9wf2ps4z there is nothing to play with java 8 in above question , i have tried below approach pls have a look import java.util.regex.Matcher; import java.util.regex.Pattern; public class SwapAdjacentNumericValues { public static void main(String[] args) { String input = "ab45cfd23"; String output = swapAdjacentNumericValues(input); System.out.println(output); } private static String swapAdjacentNumericValues(String input) { StringBuilder result = new StringBuilder(); Pattern pattern = Pattern.compile("\\d+"); Matcher matcher = pattern.matcher(input); int lastIndex = 0; while (matcher.find()) { int start = matcher.start(); int end = matcher.end(); // Append the characters between the last index and the start of the current match result.append(input.substring(lastIndex, start)); // Append the current numeric value result.append(input, start, end); lastIndex = end; } // Append the remaining characters after the last numeric value result.append(input.substring(lastIndex)); return result.toString(); } }

[@user-cz9wf2ps4z]

tq for ur response@@Javatechie

[@revathiruby8541]

I have done all the configuration but its taking 15mins

[@Javatechie]

What’s your core configuration?

[@revathiruby8541]

@@Javatechie @enablesync and needed configuration i have done

[@Yigrite]

One suggestion: Please do reduce the length of introduction video

[@Javatechie]

Buddy i always wanted to clear base/context/fundamental rather than simply doing code. Btw you still have the option to skip it right 🤣

[@Yigrite]

@@Javatechie Your content was just amazing bro , yea i can skip it , but still it's a suggestion 🙂

[@MarkMorales-du1nh]

@@Javatechie You're already doing good bro, you don't need to take his suggestion. I love it when you explain the use case in more detail. Thanks for your amazing video! I subscribed.

[@saimonldable]

Skip right

[@Yigrite]

@@MarkMorales-du1nh guys i meant the intro, not the whole video length 😒

[@mymailg6663]

The world is moving towards reactive programming, why don't you explain the examples in webflux instead of simple spring web

[@Javatechie]

Wwbflux already explained please check

[@mymailg6663]

@@Javatechie I am saying slowly having example in terms of newly employed tech will help a lot. Yes I know webflux video is there and is awesome