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

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.
主站蜘蛛池模板: 江城| 韶关市| 广安市| 临潭县| 安岳县| 平远县| 满洲里市| 承德市| 长寿区| 宝应县| 托克逊县| 靖西县| 张家港市| 囊谦县| 隆回县| 吐鲁番市| 柘城县| 潞城市| 社旗县| 平湖市| 苍溪县| 无极县| 阳西县| 都安| 宿迁市| 扬州市| 福安市| 梁山县| 施甸县| 磴口县| 永嘉县| 新蔡县| 眉山市| 宁乡县| 海宁市| 锡林浩特市| 洞口县| 繁昌县| 论坛| 上杭县| 阿克陶县|