SaaS Tips: Part Two
来源： 作者： 发布时间：2007-08-17
|
|
|
Yesterday I shared with you some best practices of the SaaS model. Today we’re talking about security and performance and everything that comes with it.
As we’ve seen with the Gartner report and here, the SaaS model is here to stay! And with SaaS - everything hinges on trust – guard it carefully. Don’t plan on second chances – if the application is unreliable, the site is often unavailable, data security is compromised or data are lost, you will lose both credibility and customers.
So let’s continue with part two of SaaS Tips….
Reliability
–Build in automatic fail-over
–Monitor aggressively
–Backup
Strive for at least three 9’s of reliability – this translates into less than 45 minutes of unscheduled downtime per month. To accomplish this, architect your site with automatic fail-over and eliminate (or mitigate) all single points of failure. Aggressively monitor the application, not only to quickly react to issues but also to proactively predict trouble spots, such as progressively increasing CPU utilization. 数据挖掘
Develop a backup strategy that fully protects your data and provides for both individual file restore and full site reconstruction. If all else fails, you must be able to recreate lost or corrupted data.
Security
Customers are entrusting you with their data – often confidential in nature. They must be fully confident that your security process and associated infrastructure protect against unauthorized access. Think hard about creating a documented, formal security policy to both ensure appropriate security and to use as a vehicle for communicating your security policy to prospects and customers.
Scalability
Build your application to scale effectively. Test it with several times the expected throughput, to gain confidence that the site will not suddenly become unavailable due to an unexpected influx of customers.
Design for your user base
Bandwidth is the lifeblood of hosted applications. If your users are small satellite offices, don’t expect them to have high bandwidth connections. Create an application that works well in your targeted environment.
Don’t host it yourself
To restate the overall premise – everything hinges on trust. A co-location facility provides redundant power, redundant Internet connectivity, adequate cooling, physical security, fire mitigation, and other benefits that allow you to obtain the reliability and security needed to meet your SLA.
Do you have any time tested best practices you’d recommend? Let me know!
-Joe
|
|
|
|
|
|
|
|
|
|
