I'm a bit concerned regarding enkompass scalability when using remote storage.
The way I see it, Enkompass should support creating pools of web servers each with their own storage point.
This way it's really scalable as you add, let's say, 4 or 5 web servers to the same pool and assign a shared remote storage to them.
Then, when it fills up, you close that pool and create another one of 4 or 5 web servers and assign another shared storage to them.
There are many advantages to this approach specially:
- Scalability
- Maintenance
- Performance
Sites failover would only be possible inside the same pool but even I see this as a benefit.
In a 50.000 user scenario, considering you put 500 users per server and each user uses 2GB average, without the pool feature you would need 100 web servers sharing the same 100TB storage with a over exaggerated failover farm and each domain would also have 100 A record entries for each of the webservers.
With the pool feature, you would have the same 100 web servers, but split in smaller farms of 5 servers each with a shared storage of 5TB per farm where each domain would have at max 5 A records in their DNS.
Update:
Anyway, I just got an update from Cpanel in which they're planning to introduce later on multiple farms (pools as I described it).



LinkBack URL
About LinkBacks
Reply With Quote





