# Same parent project on multiple Front Ends - Scale-Out/Hub and Spoke Architecture **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [May 9, 2019, 3:40pm UTC](https://forum.inductiveautomation.com/t/same-parent-project-on-multiple-front-ends-scale-out-hub-and-spoke-architecture/24842 "2019-05-09T15:40:29Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\ **Post date:** [May 9, 2019, 4:05pm UTC](https://forum.inductiveautomation.com/t/same-parent-project-on-multiple-front-ends-scale-out-hub-and-spoke-architecture/24842/2 "2019-05-09T16:05:36Z")
You share the project manually: > [@Load Balancer - Need some help](http://forum.inductiveautomation.com/t/load-balancer-need-some-help/24495/2): > > Yes, an external load balancer. Manually. Via the gateway network and the Enterprise Administration Module. Or entirely manually, with gateway backups or scripted with a great deal of knowledge of the guts of Ignition. Project synchronization is planned, but a ways out: > [@Load Balancer - Need some help](http://forum.inductiveautomation.com/t/load-balancer-need-some-help/24495/3): > > To expand a bit: we didn’t implement load balancing, because nothing we can possible implement will ever approach the feature set and reliability of a proven tool like [nginx](https://www.nginx.com/) - load balancing HTTP traffic (which, ultimately, is all both Vision and Perspective use) is a “solved problem”, so we didn’t want to reinvent the wheel. Project synchronization between gateways is something we plan on improving as a larger push to expand and improve EAM, but that will likely be in future major versions, no… --- _[View the full topic](https://forum.inductiveautomation.com/t/same-parent-project-on-multiple-front-ends-scale-out-hub-and-spoke-architecture/24842)._