-
Notifications
You must be signed in to change notification settings - Fork 4
Expand file tree
/
Copy pathexample.json
More file actions
21 lines (20 loc) · 1.7 KB
/
example.json
File metadata and controls
21 lines (20 loc) · 1.7 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
{
"questions_and_answers": [
{
"question": "Provide a title of your cloud system architecture and a brief description",
"answer": "The cloud system architecture is called 'Events Processing Architecture' and it is hosted on AWS."
},
{
"question": "What are the resources used in this cloud system architecture? Specify the cloud provider if it is among supported cloud providers.",
"answer": "Web Service from Amazon Compute EKS, Events Storage of S3 type from AWS, Events Analytics service from AWS Database Redshift, Events Queue from AWS SQS, Three Workers from AWS ECS Compute with designations of N1, N2, and N3, Three Processing Lambdas from AWS Lambda Compute with designations of N1, N2, and N3."
},
{
"question": "How are these cloud provider resources clustered or grouped? Describe in detail.",
"answer": "There is an Events Flow Cluster which contains: an Events Queue, a Workers Cluster that consists of the three defined workers (N1, N2, N3) grouped together, and a Processing Cluster that consists of a group of three processing lambdas (N1, N2, N3)."
},
{
"question": "Describe the relationships between these resources and clusters/groups.",
"answer": "The Web Service passes data to the Workers Cluster within the Events Flow Cluster. The Events Queue in the Events Flow Cluster relates to the Processing Cluster containing the lambdas in an outgoing direction. The Workers Cluster passes data to the Events Queue in an outgoing direction. The Processing Cluster containing the compute lambdas has outgoing relationships to both the Events Storage (S3) and Events Analytics (Redshift) services."
}
]
}