Resources and uptime
In a shared AWS environment, LoanPro makes decisions on scaling the hardware and services used to make the software function. In order to scale hardware efficiently, LoanPro has implemented auto-scaling. This monitors usage levels of current hardware and services, and then deploys new resources to spin up and provision new hardware.
Each customer in the shared AWS environment has a dedicated database for each tenant—meaning those who have a sandbox and a production account will have two separate databases. LoanPro is designed to operate optimally as multiple customers use services like database connections, processing power, and AWS. However, using a shared environment can sometimes slow down resources. Below, we outline the best practices to ensure uptime and speed.
Some clients pay additional fees for dedicated hardware or a separate AWS environment, in which case they don't need to worry about their resources being shared with and slowed down by other clients. If that interests you, speak to our sales team or success specialists about upgrading to a VPC account.
LoanPro uptime and speed
In order for LoanPro to meet our stated uptime and speed needed for our software to operate acceptably, customers should pay special attention to the following excessive use concerns including, but not limited to:
- API calls in both volume and frequency
- Number of loans in their tenant (LoanPro account)
- Database connections
- Number of rules
- Etc.
Your LoanPro contact can help you determine the right limits for these features and let you know when it may be time to upgrade your environment. If usage of these areas is high, the client is responsible to authorize LoanPro's recommendations for resources. Continuous usage near or at the design limits for hardware are a mitigating circumstance and LoanPro is not required to meet uptime or issue statement credits for those customers.
Security
Security is paramount to LoanPro and our clients. We employ coding practices, software, and procedures to keep data within the software secure. This includes measures to guard against:
- DDOS attacks
- Man-in-the-middle attacks
- SQL injection
- Unauthorized authentication
- System intrusion
- Etc.
Was this article helpful?