# Node-red use as a full stack backend?

**URL:** <https://discourse.nodered.org/t/node-red-use-as-a-full-stack-backend/50392>\
**Category:** General\
**Created:** [30 August 2021 14:30 UTC](https://discourse.nodered.org/t/node-red-use-as-a-full-stack-backend/50392 "2021-08-30T14:30:53Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![janvda](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/janvda/32/234_2.png) [@janvda](https://discourse.nodered.org/u/janvda)\
**Post date:** [1 October 2021 12:14 UTC](https://discourse.nodered.org/t/node-red-use-as-a-full-stack-backend/50392/15 "2021-10-01T12:14:32Z")

</div>

> [@Peter](#):
>
> will it be able to handle millions of API calls / web endpoints per day when its required to do?

Just wondering how node-red can be scaled horizontally to address big loads.

I am thinking that this should happen by starting multiple instances of the same node-red application and assuring that traffic is load balanced amongst the different instances.

If your application is changing data or need to keep track of the user context then this should be considered so that it can be scaled horizontally by spinning up multiple instances.

---

_[View the full topic](https://discourse.nodered.org/t/node-red-use-as-a-full-stack-backend/50392)._
