官术网_书友最值得收藏!

System architecture

At first glance, a three-tier web application using a REST API can be an easy topic and pattern. After all, there are only three layers, which are responsible for very discrete tasks, and the final result is just a web application after all. However, there are many nuances and areas for tweaking with any web application. Serverless web applications are no different. This chapter will attempt to cover as many areas as possible, but it's impossible to include every possible configuration or design option.

Seeing as we are responsible software designers, let's sketch out our architecture at a high level and drill down into more detail as we work through the different layers:

This diagram should look familiar as it's the backbone of many client-server web applications out there today. Let's walk through the different layers, going from the top down. After discussing these layers at a high level, we'll get into the implementation details with a real-world example.

You can find all of the code in this chapter in the following repository:

https://github.com/brianz/serverless-design-patterns/tree/master/ch2

Even though a common and arguably simple pattern, there are many possible complexities when deploying a stack like this on AWS with a serverless architecture. While AWS is the PaaS of choice for this and subsequent chapters, there are many topics that cannot be covered in great depth due to the size of AWS as a topic by itself. If you get stuck or are confused by any missing content, feel free to open a GitHub issue at the preceding repository to begin a dialog and I'll do my best to help.
主站蜘蛛池模板: 醴陵市| 读书| 搜索| 河东区| 桃园市| 十堰市| 汉沽区| 修文县| 乐陵市| 山西省| 靖西县| 乐平市| 四川省| 容城县| 上蔡县| 陕西省| 长兴县| 三穗县| 万安县| 南充市| 大同县| 容城县| 南城县| 正安县| 揭西县| 宜君县| 洛川县| 盈江县| 莫力| 福海县| 喜德县| 连山| 体育| 绍兴市| 陈巴尔虎旗| 芜湖市| 怀仁县| 太白县| 涟水县| 芜湖县| 文化|