# What is the advantage of async views? Why is adrf mentioned in Existing Third Party Packages? **URL:** \ **Category:** Async\ **Created:** [June 27, 2025, 9:33am UTC](https://forum.djangoproject.com/t/what-is-the-advantage-of-async-views-why-is-adrf-mentioned-in-existing-third-party-packages/41596 "2025-06-27T09:33:53Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\ **Post date:** [June 27, 2025, 1:54pm UTC](https://forum.djangoproject.com/t/what-is-the-advantage-of-async-views-why-is-adrf-mentioned-in-existing-third-party-packages/41596/2 "2025-06-27T13:54:54Z")
> [@SimonVitt](#): > > Is there any case where async views in Django provide a real-world scalability or performance win? Yes. The archtypal example is a situation where one request needs to call “n” external APIs. Let’s say you’re running some type of “aggregator” service for hotel room availability. You might want to issue API requests to all of `booking.com`, `expedia.com`, `hotels.com`, etc. Those calls (and the processing of their responses) could be handled in parallel by calling them and using a `gather` to wait for them all to complete before returning the response. > [@SimonVitt](#): > > Given that, wouldn’t the sync version be simpler and just as efficient (or even more)? `` Yes. The benefits of going async tend to be overstated and address a relatively small percentage of deployment environments. `` I’ve written about this at length in multiple places here, such as at [What does switching to ASGI entail? - #2 by KenWhitesell](https://forum.djangoproject.com/t/what-does-switching-to-asgi-entail/26857/2) --- _[View the full topic](https://forum.djangoproject.com/t/what-is-the-advantage-of-async-views-why-is-adrf-mentioned-in-existing-third-party-packages/41596)._