Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Essay: The trend of distributed software architecture #1031

Merged
merged 1 commit into from
Mar 30, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions contributions/essay/kunwu/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Essay: The trend of distributed software architecture
## An envolving analysis of different architectural design in distributed services

### Members
Kun Wu (kunwu@kth.se)
GitHub: [Wkkkkk](https://github.com/Wkkkkk)

### Proposal

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

A rolling stone gathers no moss. Devops, as part of system infrastructure, ensure that every single service in the whole system can die and reboot without disturbing the overall performance.

This paper talks about how this sustainability is addressed in different architectural styles.