Essay submission: An exploration of the evolving software architecture

contributions/essay/kunwu-bouaddi/README.md

@@ -0,0 +1,41 @@
+# Essay: The trend of distributed software architecture
+## An envolving analysis of different architectural design in distributed services
+
+### Members
+Kun Wu ([email protected])
+GitHub: [Wkkkkk](https://github.com/Wkkkkk)
+
+Hilaire Bouaddi ([email protected])
+GitHub: [Hilaire-Bouaddi](https://github.com/Hilaire-Bouaddi)
+
+### Topic
+
+How to build a large-scale stable system if its components could possibly fail? This has been a issue for
+many years. 
+
+In this paper, I'll describe how software architecture has been evolving to address this issue, from [Mainframe computer](https://en.wikipedia.org/wiki/Mainframe_computer), to [Distributed computing](https://en.wikipedia.org/wiki/Distributed_computing), to [Monolithic application](https://en.wikipedia.org/wiki/Monolithic_application), to [Service-oriented architecture](https://en.wikipedia.org/wiki/Service-oriented_architecture), to [Microservices](https://en.wikipedia.org/wiki/Microservices), to [Service Mesh](https://en.wikipedia.org/wiki/Service_mesh), to [Serverless computing](https://en.wikipedia.org/wiki/Serverless_computing), etc..
+
+Through the this ever-changing trend, we can have a holistic view of how possible failure is handled in different times and how to build up automated exception handling which ensures a stable and robust performance.
+
+
+### Suitability of Topic
+###Grading criteria we aim for:
+
+|                                             | Yes | No | Remarkable |
+|-------------------------------------------- | ----|----|-------------|
+| format: The essay is in PDF | :heavy_check_mark: Mandatory | - | - |
+| title: The essay has a good title | Yes | No | :heavy_check_mark: Remarkable |
+| well-structured: The essay is well structured, the ideas are well presented | Yes | No | :heavy_check_mark: Remarkable |
+| introduction: The essay contains a good introduction | :heavy_check_mark: Yes | No | Remarkable |
+| conclusion: The essay contains a good conclusion | :heavy_check_mark: Yes | No | Remarkable |
+| self-contained: The essay is self-contained, one can understand it without reading something else (expected knowledge of the reader: a master student in computer science) | Yes | No | :heavy_check_mark: Remarkable |
+| innovative: The essay contains innovative ideas or material | :heavy_check_mark: Yes | No | Remarkable |
+| figures: The essay contains good figures or listings | Yes | No | :heavy_check_mark: Remarkable |
+| sound: The essay is sound, factual, and accurate | :heavy_check_mark: Yes | No | Remarkable |
+| references: The essay contains references, appropriate  in number and quality (10 good refs is a minimum) | :heavy_check_mark: Yes | No | Remarkable |
+| elegant: The essay presentation is elegant / visually appealing (eg LaTeX, InDesign) | Yes | No | :heavy_check_mark: Remarkable |
+| relevant: The essay addresses a topic that is relevant for DevOps | Yes | No | :heavy_check_mark: Remarkable |
+
+
+## Feedback
+Receiving feedback from [Ayub Atif]([email protected]) and [Isac Arvidsson]([email protected]). PR ID [#1072](https://github.com/KTH/devops-course/pull/1072)

contributions/feedback/kunwu/README.md

@@ -0,0 +1,21 @@
+# Feedback on FaaS, Serverless, Containerization, and DevOps
+### Members
+Kun Wu ([email protected])
+GitHub: [Wkkkkk](https://github.com/Wkkkkk)
+
+### Proposal
+A feedback on this essey [#952](https://github.com/KTH/devops-course/pull/952) by [Taqui]([email protected]) has been given.
+See it [here](https://github.com/KTH/devops-course/pull/952#issuecomment-824708343).
+
+
+###Grading criteria we aim for:
+
+|                                             | Yes | No | Remarkable  |
+|-------------------------------------------- | ----|----|-------------|
+|The feedback includes both strengths and weaknesses about the task | :heavy_check_mark: Yes | No | n-a |
+|The feedback is provided 4 business days before the task deadline | Yes | No | :heavy_check_mark: Within 24h after the task submission |
+|All points are clearly actionable | :heavy_check_mark: Yes | No | PR on PR |
+|The feedback is substantiated | :heavy_check_mark: Yes (at least 500 words) | No | At least 1000 words |
+|The feedback contains pointers to additional material | Yes | No | :heavy_check_mark: One pointer is less than one week |
+|The students  act upon the feedback they receive | :heavy_check_mark: Yes | No | Document the changes made after feedback|
+