-
Notifications
You must be signed in to change notification settings - Fork 426
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Essay: The trend of distributed software architecture (#1031)
- Loading branch information
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |