OBJECTIVES
• Use external publicly available resources to gain skills and knowledge necessary to design cloud-based event-driven solutions.
• Propose a cloud-based web application amenable to an event-driven solution
• Complete a technical architectural design for the proposed application
WEB APP REQUIREMENTS
This is an open assignment where you will define the functional requirements of a cloud-based web application of your choice. You might get some inspiration for the examples of possible scenarios with high-level architecture have been included in the Resources section below.
The definition of requirements for your application should contain the following:
• Statement of the purpose of the application.
• A use-case for each type of user.
• A statement of the functional requirements.
Keep in mind that your application needs to be complex enough to necessitate the inclusion of the range of services specified in the Architecture Design Requirements section below.
There is no need to specify the non-functional requirements of your application. However, the application does need to have the following properties:
• Scale according to demand
• Be highly available
• Be decoupled so that it can easily be modified and extended
• Data storage with 99.99% availability
• Be secure from external attack
ARCHITECTURE DESIGN REQUIREMENTS
Once you have specified the requirements for your application you need to produce a technical software design for it that will run on AWS. As well as using IAM to define security roles, your web app MUST incorporate as a minimum the following AWS services:
• AWS API Gateway (at least two different services APIs should be invoked)
• AWS Simple Notification Service (SNS)
• AWS Lambda
• AWS DynamoDB (durable data needs to be stored on DynamoDB)
It is very likely that you will need additional services such as S3, SQS, Network services, Cognito, CloudFront, Route53, CloudWatch, Kinesis, AI services etc. as appropriate. The use of services we have not covered in the lectures / labs is encouraged.
Your design document must include the following sections:
1. An architectural diagram showing the VPC network and cloud services used. To draw an architecture diagram, you could use draw.io (www.draw.io/?splash=0&libs=aws4) or any other tools you see fit (www.aws.amazon.com/architecture/icons/
2. A description of each of the functional services used in your design. This should include:
a. The brief description of the function of each service.
b. The interface definition for each service.
c. If appropriate, discuss why you selected that service over other alternatives.
3. UML collaboration diagram(s) showing the interactions between the user and services. Order of messages should be shown. All use cases should be documented. Alternatively, a UML sequence diagram(s) can be used.
USEFUL RESOURCES
What is an Event-Driven Architecture? Decoupled systems that run in response to events.
• AWS Compute Blog: Enriching Event-Driven Architectures with AWS Event Fork Pipelines
• Find the hands-on tutorials and training videos for your AWS needs. Get started with simple step-by-step tutorials to launch your first workload.
• AWS Compute Blog: Event-Driven Computing with Amazon SNS and AWS Compute, Storage, Database, and Networking Services
• AWS Blog in general. You can filter the blogs by a number of different categories such as Compute, Architecture, DevOps, etc. This is a great and very hands-on resource.
Document Checklist
□ FRONT MATTER
□ Title page
□ Table of Contents
□ WEB APP REQUIREMENTS
□ Statement of the purpose of the application.
□ A use-case for each type of user
□ A statement of the functional requirements.
□ ARCHITECTURE DESIGN
□ Architecture diagram
□ Service Descriptions
Function.
Interface definition
Rationale
□ Collaboration or sequence diagram
The post resources to gain skills and knowledge appeared first on My Assignment Online.