Workload Requirements for E-Mail
BallotOnline’s e-mail solution needs to be able to accommodate the following requirements:
- Recovery time objective = 15 minutes
- Recovery point objective = 0 minutes (no data loss acceptable)
- Mailboxes = 5,000 minimum, scalable to 10,000
- Solution needs to be completely owned and supported by the vendor
- Per user or mailbox monthly billing
- Multifactor authentication and encryption support
Workload Requirements for Software Development
BallotOnline’s software development solution needs to be able to accommodate the following requirements:
- Recovery time objective = 0 minutes (always available)
- Recovery point objective = 15 minutes (15 minutes worth of work/data loss acceptable)
- Number of users = 5,000 minimum, scalable to 10,000
- Infrastructure, application, and middleware needs completely owned and supported by the vendor
- Data storage capacity = 1 TB per sandbox/user
- Maximum number of IOPS (input/output operations per second) per sandbox/user = 15,000
- Minimum number of IOPS per sandbox/user = 5,000
- Highest acceptable round trip latency = 2 ms
- Per user monthly billing
- Multifactor authentication and encryption at rest support
Workload Requirements for Backups and Archiving
The workload requirements for backups and archiving for BallotOnline need to reflect the following:
- Recovery time objective = 30 minutes
- Recovery point objective = 30 minutes (30 minutes worth of work/data loss acceptable)
- Infrastructure needs to be completely owned and supported by the vendor
- Data storage capacity = 1 PB
- Maximum number of IOPS (input/output operations per second) per sandbox/user = 500
- Minimum number of IOPS per sandbox/user = 100
- Highest acceptable round trip latency = 150ms
- Per user monthly billing
- Multifactor authentication and encryption at rest support
Cloud Deployment Architecture Plan
Your final cloud deployment architecture plan should be 5 to 10 pages in length in either Microsoft Word or PDF format. The report should contain the following headings:
- Executive Summary (< 1 page)
- Scope (<1 page)
- Evaluation of Cloud Service Offering Architecture for E-Mail (1 page)
- Evaluation of Cloud Service Offering Architecture for Software Development (1 page)
- Evaluation of Cloud Service Offering Architecture for Backup and Archiving (1 page)
- Architecture Design for E-Mail in the Cloud (1 page)
- Architecture Design for Software Development Platform in the Cloud (1 page)
- Architecture Design for Backup and Archiving in the Cloud (1 page)
- Cloud Monitoring Solution for Backup and Archiving (1–2 pages)
- Limitations (<1 page)
- Summary (<1 page)