mojoPortal Tips: mojoPortal and Scalability
Written by Carole Bennett Tuesday, 28 August 2012
One of the biggest frustrations of any website is when it outgrows capacity. Luckily for mojoPortal users, there are multiple methods of configuring a mojoPortal-based site to be not only flexible, but expand with the needs of your organization.
Method 1: Flexible Hosting – leveraging a hosting option such as a VPS can allow you to increase available resources to a specific website instance. Since this is a single-server solution, the complex issues of load-balancing, etc. are not relevant factors.
Method 2: Scalable Hosting – Cloud-based hosting, such as Microsoft Azure or Amazon AWS EC2 are dynamically scalable options, which can allow you to only pay for peak-time resources when required, and scale back down to use less resources during less use-intensive periods. mojoPortal has been implemented on Microsoft Azure; you can find more information on how to do so on the mojoPortal.com site.
Method 3: Web Farm – This method can also be leveraged for mojoPortal. Direction and caveats for web farms can be found here: Implementation Considerations for Web Farms, and discussions on successful implementations can be found in the mojoPortal forums, such as this thread: “Web Farm Support”.
Factors to consider when deciding scalability include:
1) Number of users: how many site visitors vs. registered members?
2) Number of sites/unique records/documents – will this be a multi-site implementation, or encompass multiple regions/divisions?
3) Technical resources – will the hosting environment be supported in-house, on machines managed by the organization, outsourced to a managed hosting environment, or a solution that falls somewhere in between?
When planning scalability, look at your business plan, work with your lines of business, and your technical resources to determine which solution is best for you.