Cloud Architecture – Project
BRIEF
Imagine you meet a small startup company planning to launch a new mobile application that allows consumers & service providers to interact real time. Currently their architecture uses a LAMP stack comprising of open source software. Like many small start-ups they are confident that they will be the next big thing and expect significant, rapid, yet un-quantified growth in the next few months. With this in mind, they are concerned about the following:
- Scaling to meet the demand, but with uncertainty around when and how much this demand will be – they are very concerned about buying too much infrastructure too soon or not enough too late!
- Disaster Recovery planning
- Manage user identities & sync user specific data across multiple devices
- Ability for Service Providers to send notifications to consumer
- Ability to run analytics on top of collected data, with analytics they should be able to visualize & understand app data usage
- Their ability to configure their database and data access layer for high performance and throughput
- Effective distribution of load
- A self-healing infrastructure that recovers from failed service instances
- Security of data at rest and in transit
- Securing access to the environment as the delivery team expands
- An archival strategy for inactive objects greater than 6 months
- Ability to easily manage and replicate multiple environments based on their blueprint architecture
OBJECTIVE
Recommend a manageable, secure, scalable, high performance, efficient, elastic, highly available, fault tolerant and recoverable architecture that allows the startup to organically grow. The architecture should specifically address the requirements/concerns as described above.
DELIVERABLES
- A Solution Document in PDF format, no greater than three pages in length that clearly & succinctly presents a solution addressing the startups requirement.
- Solution document must have the proposed architecture diagram & explanation how the solution will flow.
- Clearly state all assumptions made during the design and explicitly state the referenced AWS Services if used in the design.
- You can present your solution either On-Premise Datacenter or any other public cloud vendor based solution.
