# Client side data from external source

**URL:** <https://community.plotly.com/t/client-side-data-from-external-source/41118>\
**Category:** Dash Python\
**Created:** [June 16, 2020, 3:39pm UTC](https://community.plotly.com/t/client-side-data-from-external-source/41118 "2020-06-16T15:39:32Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Fernandes](https://avatars.discourse-cdn.com/v4/letter/f/94ad74/32.png) [@Fernandes](https://community.plotly.com/u/Fernandes)\
**Post date:** [August 25, 2020, 11:22am UTC](https://community.plotly.com/t/client-side-data-from-external-source/41118/9 "2020-08-25T11:22:18Z")

</div>

In my particular use case it’s user specific data, each user as it own data. That needs to be fetch from an external server.  
I can see your point if the data was the same for all users. But that is not the case for me.

And I can also see what you mean in terms of speed. But imagine that you max or are closing to max out your server resources (e.g cpu, memory, etc…). The requests between the clientside and the server will take longer to be resolved.

Performing external calls in the clientside would allow to offload some of that load to the clients.  
Imagine you have 1000 clients connected to your dash server. The server has to perform 1000 requests and wait for the responses + render the layout.

While if it was in the clientside each user would perform 1 request to the external server and the server only needs to render the layouts with the information received.

---

_[View the full topic](https://community.plotly.com/t/client-side-data-from-external-source/41118)._