{"componentChunkName":"component---src-templates-blog-detail-tsx","path":"/blog/2020-04-10-website-alarm","result":{"data":{"currentBlog":{"id":"44ad21a9-00a3-592c-83c1-696af478c55f","frontmatter":{"thumbnail":"https://img.serverlesscloud.cn/2020414/1586850670017-%E5%B0%81%E9%9D%A2%E5%9B%BE%20%283%29.png","authors":["Anycodes"],"categories":["guides-and-tutorials","operations-and-observability"],"date":"2020-04-10T00:00:00.000Z","title":"Serverless 实战：通过 Serverless 架构实现监控告警","description":"Serverless 的一个重要应用场景就是运维、监控与告警，本文将会通过现有的 Serverless 平台，部署一个网站状态监控脚本，对网站的可用性进行监控告警","authorslink":["https://www.zhihu.com/people/liuyu-43-97"],"translators":null,"translatorslink":null,"tags":["Serverless","监控告警"],"keywords":"Serverless 全局变量组件,Serverless 单独部署组件,Serverless Component","outdated":true},"wordCount":{"words":368,"sentences":65,"paragraphs":65},"fileAbsolutePath":"/opt/build/repo/content/blog/2020-04-10-website-alarm.md","fields":{"slug":"/blog/2020-04-10-website-alarm/","keywords":["php","python","serverless","监控","告警","Serverless","耗时","网站"]},"html":"

在实际生产中，我们经常需要做一些监控脚本来监控网站服务或者 API 服务是否可用。传统的方法是使用网站监控平台（例如 DNSPod 监控、360 网站服务监控，以及阿里云监控等），它们的原理是通过用户自己设置要监控的服务地址和监测的时间阈值，由监控平台定期发起请求对网站或服务的可用性进行判断。

\n

这些方法很大众化，通用性很强，但也不是所有场景都适合。例如，如果我们的需求是监控网站状态码，不同区域的延时，并且通过监控得到的数据，设定一个阈值，一旦超过阈值就通过邮件等进行统治告警，目前大部分的监控平台是很难满足这些需求的，这时就需要定制开发一个监控工具。

\n

Serverless 服务的一个重要应用场景就是运维、监控与告警，所以本文将会通过现有的 Serverless 平台，部署一个网站状态监控脚本，对目标网站的可用性进行监控告警。

\n

Web 服务监控告警

\n

针对 Web 服务，我们先设计一个简单的监控告警功能的流程：

\n

\"Serverless

\n

在这个流程中，我们仅对网站的状态码进行监控，即返回的状态为 200，则判定网站可正常使用，否则进行告警：

\n\n \n 复制代码\n \n \n
# -*- coding: utf8 -*-\nimport ssl\nimport json\nimport smtplib\nimport urllib.request\nfrom email.mime.text import MIMEText\nfrom email.header import Header\n\nssl._create_default_https_context = ssl._create_unverified_context\n\n\ndef sendEmail(content, to_user):\n    sender = 'service@anycodes.cn'\n    receivers = [to_user]\n\n    mail_msg = content\n    message = MIMEText(mail_msg, 'html', 'utf-8')\n    message['From'] = Header(\" 网站监控 \", 'utf-8')\n    message['To'] = Header(\" 站长 \", 'utf-8')\n\n    subject = \" 网站监控告警 \"\n    message['Subject'] = Header(subject, 'utf-8')\n\n    try:\n        smtpObj = smtplib.SMTP_SSL(\"smtp.exmail.qq.com\", 465)\n        smtpObj.login('发送邮件的邮箱地址', '密码')\n        smtpObj.sendmail(sender, receivers, message.as_string())\n    except smtplib.SMTPException as e:\n        print(e)\n\n\ndef getStatusCode(url):\n    return urllib.request.urlopen(url).getcode()\n\n\ndef main_handler(event, context):\n    url = \"http://www.anycodes.cn\"\n    if getStatusCode(url) == 200:\n        print(\" 您的网站 %s 可以访问！\" % (url))\n    else:\n        sendEmail(\" 您的网站 %s 不可以访问！\" % (url), \" 接受人邮箱地址 \")\n    return None
\n

通过 ServerlessFramework 可以部署，在部署的时候可以增加时间触发器：

\n\n \n 复制代码\n \n \n
MyWebMonitor:\n  component: \"@serverless/tencent-scf\"\n  inputs:\n    name: MyWebMonitor\n    codeUri: ./code\n    handler: index.main_handler\n    runtime: Python3.6\n    region: ap-guangzhou\n    description: 网站监控\n    memorySize: 64\n    timeout: 20\n    events:\n      - timer:\n          name: timer\n          parameters:\n            cronExpression: '*/5 * * * *'\n            enable: true
\n

在这里，timer 表示时间触发器，cronExpression是表达式：

\n

创建定时触发器时，用户能够使用标准的 Cron 表达式的形式自定义何时触发。定时触发器现已推出秒级触发功能，为了兼容老的定时触发器，因此 Cron 表达式有两种写法。

\n

Cron 表达式语法一（推荐）

\n

Cron 表达式有七个必需字段，按空格分隔。\n\"Serverless\n其中，每个字段都有相应的取值范围：

\n

\"Serverless

\n

Cron 表达式语法二（不推荐）

\n

Cron 表达式有五个必需字段，按空格分隔。\n\"Serverless\n其中，每个字段都有相应的取值范围：\n\"Serverless

\n

通配符

\n

\"Serverless

\n

注意事项

\n

在 Cron 表达式中的“日”和“星期”字段同时指定值时，两者为“或”关系，即两者的条件分别均生效。

\n

示例

\n

*/5 * * * * * * 表示每 5 秒触发一次\n0 0 2 1 * * * 表示在每月的 1 日的凌晨 2 点触发\n0 15 10 * * MON-FRI * 表示在周一到周五每天上午 10：15 触发\n0 0 10,14,16 * * * * 表示在每天上午 10 点，下午 2 点，4 点触发\n0 */30 9-17 * * * * 表示在每天上午 9 点到下午 5 点内每半小时触发\n0 0 12 * * WED * 表示在每个星期三中午 12 点触发

\n

因此，我们上面的代码可以认为是每 5 秒触发一次，当然，也可以根据网站监控密度，自定义设置触发的间隔时间。当我们网站服务不可用时，就可以收到告警：

\n

\"Serverless

\n

这种网站监控方法比较简单，准确度可能会有问题，对于网站或服务的监控不能简单的看返回值，还要看链接耗时、下载耗时以及不同区域、不同运营商访问网站或者服务的延时信息等。

\n

所以，我们需要对这个代码进行额外的更新与优化：

\n
    \n
  1. 通过在线网速测试的网站，抓包获取不同地区不同运营商的请求特征；
    2. \n
  2. 编写爬虫程序，进行在线网速测试模块的编写；
    3. \n
  3. 集成到刚刚的项目中；
    4. \n
\n

下面以站长工具网站中国内网站测速工具 为例，通过网页查阅相关信息。

\n

对网站测速工具进行封装，例如：

\n

\"Serverless

\n

通过对网页进行分析，获取请求特征，包括 Url，Form data，以及 Headers 等相关信息，其中该网站在使用不同监测点对网站进行请求时，是通过 Form data 中的 guid 的参数实现的，例如部分监测点的 guid：

\n\n \n 复制代码\n \n \n
广东佛山\t电信\tf403cdf2-27f8-4ccd-8f22-6f5a28a01309\n江苏宿迁\t多线\t74cb6a5c-b044-49d0-abee-bf42beb6ae05\n江苏常州\t移动\t5074fb13-4ab9-4f0a-87d9-f8ae51cb81c5\n浙江嘉兴\t联通\tddfeba9f-a432-4b9a-b0a9-ef76e9499558
\n

此时，我们可以编写基本的爬虫代码，来对 Response 进行初步解析，以62a55a0e-387e-4d87-bf69-5e0c9dd6b983 江苏宿迁 [电信]为例，编写代码：

\n\n \n 复制代码\n \n \n
import urllib.request\nimport urllib.parse\n\nurl = \"* 某测速网站地址 *\"\nform_data = {\n    'guid': '62a55a0e-387e-4d87-bf69-5e0c9dd6b983',\n    'host': 'anycodes.cn',\n    'ishost': '1',\n    'encode': 'ECvBP9vjbuXRi0CVhnXAbufDNPDryYzO',\n    'checktype': '1',\n}\nheaders = {\n    'Host': 'tool.chinaz.com',\n    'Origin': '* 某测速网站地址 *',\n    'Referer': '* 某测速网站地址 *',\n    'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.108 Safari/537.36',\n    'X-Requested-With': 'XMLHttpRequest'\n}\n\nprint(urllib.request.urlopen(\n    urllib.request.Request(\n        url=url,\n        data=urllib.parse.urlencode(form_data).encode('utf-8'),\n        headers=headers\n    )\n).read().decode(\"utf-8\"))
\n

获得结果：

\nServer: ...',\n\t\tpagehtml: ''\n\t}\n})`, `43901181262950195000`)\"\n >\n \n 复制代码\n \n \n
({\n\tstate: 1,\n\tmsg: '',\n\tresult: {\n\t\tip: '119.28.190.46',\n\t\thttpstate: 200,\n\t\talltime: '212',\n\t\tdnstime: '18',\n\t\tconntime: '116',\n\t\tdowntime: '78',\n\t\tfilesize: '-',\n\t\tdownspeed: '4.72',\n\t\tipaddress: '新加坡新加坡',\n\t\theaders: 'HTTP/1.1 200 OK br>Server: ...',\n\t\tpagehtml: ''\n\t}\n})
\n

在这个结果中，我们可以提取部分数据，例如江苏宿迁 [电信] 访问目标网站的基础数据：

\n\n \n 复制代码\n \n \n
总耗时：alltime:'212'\n链接耗时：conntime:'116'\n下载耗时：downtime:'78'
\n

此时，我们可以改造代码对更多的节点，进行测试：

\n\n \n 复制代码\n \n \n
江苏宿迁 [电信]\t总耗时:223\t链接耗时:121\t下载耗时:81\n广东佛山 [电信]\t总耗时:44\t链接耗时:27\t下载耗时:17\n广东惠州 [电信]\t总耗时:56\t链接耗时:34\t下载耗时:22\n广东深圳 [电信]\t总耗时:149\t链接耗时:36\t下载耗时:25\n浙江湖州 [电信]\t总耗时:3190\t链接耗时:3115\t下载耗时:75\n辽宁大连 [电信]\t总耗时:468\t链接耗时:255\t下载耗时:170\n江苏泰州 [电信]\t总耗时:180\t链接耗时:104\t下载耗时:69\n安徽合肥 [电信]\t总耗时:196\t链接耗时:110\t下载耗时:73\n...
\n

并对项目中的 index.py 进行代码修改：

\n%s" % (url, "
".join(final_list)), "service@52exe.cn")`, `49924309495725970000`)\"\n >\n \n 复制代码\n \n \n
# -*- coding: utf8 -*-\nimport ssl\nimport json\nimport re\nimport socket\nimport smtplib\nimport urllib.request\nfrom email.mime.text import MIMEText\nfrom email.header import Header\n\nsocket.setdefaulttimeout(2.5)\nssl._create_default_https_context = ssl._create_unverified_context\n\ndef getWebTime():\n\n    final_list = []\n    final_status = True\n\n    total_list = '''62a55a0e-387e-4d87-bf69-5e0c9dd6b983 江苏宿迁 [电信]\n    f403cdf2-27f8-4ccd-8f22-6f5a28a01309 广东佛山 [电信]\n    5bea1430-f7c2-4146-88f4-17a7dc73a953 河南新乡 [多线]\n    1f430ff0-eae9-413a-af2a-1c2a8986cff0 河南新乡 [多线]\n    ea551b59-2609-4ab4-89bc-14b2080f501a 河南新乡 [多线]\n    2805fa9f-05ea-46bc-8ac0-1769b782bf52 黑龙江哈尔滨 [联通]\n    722e28ca-dd02-4ccd-a134-f9d4218505a5 广东深圳 [移动]\n8e7a403c-d998-4efa-b3d1-b67c0dfabc41 广东深圳 [移动]'''\n\n    url = \"* 某测速网站地址 *\"\n    for eve in total_list.split('\\n'):\n        id_data, node_name = eve.strip().split(\" \")\n        form_data = {\n            'guid': id_data,\n            'host': 'anycodes.cn',\n            'ishost': '1',\n            'encode': 'ECvBP9vjbuXRi0CVhnXAbufDNPDryYzO',\n            'checktype': '1',\n        }\n        headers = {\n            'Host': '* 某测速网站地址 *',\n            'Origin': '* 某测速网站地址 *',\n            'Referer': '* 某测速网站地址 *',\n            'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.108 Safari/537.36',\n            'X-Requested-With': 'XMLHttpRequest'\n        }\n        try:\n            result_data = urllib.request.urlopen(\n                urllib.request.Request(\n                    url=url,\n                    data=urllib.parse.urlencode(form_data).encode('utf-8'),\n                    headers=headers\n                )\n            ).read().decode(\"utf-8\")\n            try:\n                alltime = re.findall(\"alltime:'(.*?)'\", result_data)[0]\n                conntime = re.findall(\"conntime:'(.*?)'\", result_data)[0]\n                downtime = re.findall(\"downtime:'(.*?)'\", result_data)[0]\n                final_string = \"%s\\t 总耗时:%s\\t 链接耗时:%s\\t 下载耗时:%s\" % (node_name, alltime, conntime, downtime)\n            except:\n                final_string = \"%s 链接异常！\" % (node_name)\n                final_status = False\n        except:\n            final_string = \"%s 链接超时！\" % (node_name)\n            final_status = False\n        final_list.append(final_string)\n        print(final_string)\n    return (final_status,final_list)\ndef sendEmail(content, to_user):\n    sender = 'service@anycodes.cn'\n    receivers = [to_user]\n    mail_msg = content\n    message = MIMEText(mail_msg, 'html', 'utf-8')\n    message['From'] = Header(\" 网站监控 \", 'utf-8')\n    message['To'] = Header(\" 站长 \", 'utf-8')\n    subject = \" 网站监控告警 \"\n    message['Subject'] = Header(subject, 'utf-8')\n    try:\n        smtpObj = smtplib.SMTP_SSL(\"smtp.exmail.qq.com\", 465)\n        smtpObj.login('service@anycodes.cn', '密码')\n        smtpObj.sendmail(sender, receivers, message.as_string())\n    except smtplib.SMTPException:\n        pass\n\ndef getStatusCode(url):\n    return urllib.request.urlopen(url).getcode()\n\ndef main_handler(event, context):\n    url = \"http://www.anycodes.cn\"\n    final_status,final_list = getWebTime()\n    if not final_status:\n        sendEmail(\" 您的网站 %s 的状态：<br>%s\" % (url, \"<br>\".join(final_list)), \"service@52exe.cn\")
\n

由于本文是以学习为主，所以我们将节点列表进行缩减，只保留几个。通过部署，可得到结果：

\n

\"Serverless

\n

告警的灵敏度和监控的频率，在实际生产过程中可以根据自己的需求进行调整。

\n

云服务监控告警

\n

前文，我们对网站状态以及健康等信息进行了监控与告警，在实际的生产运维中，还需要对服务进行监控，例如在使用 Hadoop、Spark 的时候对节点的健康进行监控，在使用 K8S 的时候对 API 网关、ETCD 等多维度的指标进行监控，在使用 Kafka 的时候，对数据积压量，以及 Topic、Consumer 等进行监控…

\n

而这些服务的监控，往往不能通过简单的 URL 以及某些状态来进行判断。传统运维的做法是在额外的机器上设置一个定时任务，对相关的服务进行旁路监控。而在本文中，我们则通过 Serverless 技术，对云产品进行相关的监控与告警。

\n

在使用云上的 Kafka 时，我们通常要看数据积压量，因为如果 Consumer 集群挂掉了，或者消费能力突然降低导致数据积压，很可能会对服务产生不可预估的影响，这个时候对 Kafka 的数据积压量进行监控告警，就显得额外重要。

\n

本文以监控腾讯云的 Ckafka 为例进行实践，并通过多个云产品进行组合（包括云监控、Ckafka、云 API 以及云短信等）来实现短信告警、邮件告警以及企业微信告警功能。

\n

首先，可以设计简单的流程图：

\n

\"Serverless

\n

在开始项目之前，我们要准备一些基础的模块：

\n
    \n
  • Kafka 数据积压量获取模块：
    • \n
\n 2:\n sign_str = bytes(sign_str, "utf-8")\n secret_key = bytes(secret_key, "utf-8")\n hashed = hmac.new(secret_key, sign_str, hashlib.sha1)\n signature = binascii.b2a_base64(hashed.digest())[:-1]\n if sys.version_info[0] > 2:\n signature = signature.decode()\n # 签名串编码\n signature = urllib.parse.quote(signature)\n return signature\n\ndef GetGroupOffsets(max_lag, phoneList):\n param = {}\n param["Action"] = "GetGroupOffsets"\n param["instanceId"] = ""\n param["group"] = ""\n signature = GetSignature(param)\n # 生成请求地址\n param["Signature"] = signature\n url = "https://ckafka.api.qcloud.com/v2/index.php?Action=GetGroupOffsets&"\n url += "&".join("%s=%s" % (k, param[k]) for k in sorted(param))\n req_attr = urllib.request.urlopen(url)\n res_data = req_attr.read().decode("utf-8")\n json_data = json.loads(res_data)\n for eve_topic in json_data['data']['topicList']:\n temp_lag = 0\n result_list = []\n for eve_partition in eve_topic["partitions"]:\n lag = eve_partition["lag"]\n temp_lag = temp_lag + lag\n if temp_lag > max_lag:\n result_list.append(\n {\n "topic": eve_topic["topic"],\n "lag": lag\n }\n )\n print(result_list)\n if len(result_list)>0:\n KafkaLagRobot(result_list)\n KafkaLagSMS(result_list,phoneList)`, `73928739371721200000`)\"\n >\n \n 复制代码\n \n \n
def GetSignature(param):\n    # 公共参数\n    param[\"SecretId\"] = \"\"\n    param[\"Timestamp\"] = int(time.time())\n    param[\"Nonce\"] = random.randint(1, sys.maxsize)\n    param[\"Region\"] = \"ap-guangzhou\"\n    # param[\"SignatureMethod\"] = \"HmacSHA256\"\n    # 生成待签名字符串\n    sign_str = \"GETckafka.api.qcloud.com/v2/index.php?\"\n    sign_str += \"&\".join(\"%s=%s\" % (k, param[k]) for k in sorted(param))\n    # 生成签名\n    secret_key = \"\"\n    if sys.version_info[0] > 2:\n        sign_str = bytes(sign_str, \"utf-8\")\n        secret_key = bytes(secret_key, \"utf-8\")\n    hashed = hmac.new(secret_key, sign_str, hashlib.sha1)\n    signature = binascii.b2a_base64(hashed.digest())[:-1]\n    if sys.version_info[0] > 2:\n        signature = signature.decode()\n    # 签名串编码\n    signature = urllib.parse.quote(signature)\n    return signature\n\ndef GetGroupOffsets(max_lag, phoneList):\n    param = {}\n    param[\"Action\"] = \"GetGroupOffsets\"\n    param[\"instanceId\"] = \"\"\n    param[\"group\"] = \"\"\n    signature = GetSignature(param)\n    # 生成请求地址\n    param[\"Signature\"] = signature\n    url = \"https://ckafka.api.qcloud.com/v2/index.php?Action=GetGroupOffsets&\"\n    url += \"&\".join(\"%s=%s\" % (k, param[k]) for k in sorted(param))\n    req_attr = urllib.request.urlopen(url)\n    res_data = req_attr.read().decode(\"utf-8\")\n    json_data = json.loads(res_data)\n    for eve_topic in json_data['data']['topicList']:\n        temp_lag = 0\n        result_list = []\n        for eve_partition in eve_topic[\"partitions\"]:\n            lag = eve_partition[\"lag\"]\n            temp_lag = temp_lag + lag\n        if temp_lag > max_lag:\n            result_list.append(\n                {\n                    \"topic\": eve_topic[\"topic\"],\n                    \"lag\": lag\n                }\n            )\n        print(result_list)\n        if len(result_list)>0:\n            KafkaLagRobot(result_list)\n            KafkaLagSMS(result_list,phoneList)
\n
    \n
  • 接入企业微信机器人模块：
    • \n
\n\n \n 复制代码\n \n \n
def KafkaLagRobot(content):\n    url = \"\"\n    data = {\n        \"msgtype\": \"markdown\",\n        \"markdown\": {\n            \"content\": content,\n        }\n    }\n    data = json.dumps(data).encode(\"utf-8\")\n    req_attr = urllib.request.Request(url, data)\n    resp_attr = urllib.request.urlopen(req_attr)\n    return_msg = resp_attr.read().decode(\"utf-8\")
\n
    \n
  • 接入腾讯云短信服务模块：
    • \n
\n\n \n 复制代码\n \n \n
def KafkaLagSMS(infor, phone_list):\n    url = \"\"\n    strMobile = phone_list\n    strAppKey = \"\"\n    strRand = str(random.randint(1, sys.maxsize))\n    strTime = int(time.time())\n    strSign = \"appkey=%s&random=%s&time=%s&mobile=%s\" % (strAppKey, strRand, strTime, \",\".join(strMobile))\n    sig = hashlib.sha256()\n    sig.update(strSign.encode(\"utf-8\"))\n\n    phone_dict = []\n    for eve_phone in phone_list:\n        phone_dict.append(\n            {\n                \"mobile\": eve_phone,\n                \"nationcode\": \"86\"\n            }\n        )\n    data = {\n        \"ext\": \"\",\n        \"extend\": \"\",\n        \"params\": [\n            infor,\n        ],\n        \"sig\": sig.hexdigest(),\n        \"sign\": \" 你的 sign\",\n        \"tel\": phone_dict,\n        \"time\": strTime,\n        \"tpl_id\": 你的模板 id\n    }\n    data = json.dumps(data).encode(\"utf-8\")\n    req_attr = urllib.request.Request(url=url, data=data)\n    resp_attr = urllib.request.urlopen(req_attr)\n    return_msg = resp_attr.read().decode(\"utf-8\")
\n
    \n
  • 发送邮件告警模块：
    • \n
\n\n \n 复制代码\n \n \n
def sendEmail(content, to_user):\n    sender = 'service@anycodes.cn'\n    message = MIMEText(content, 'html', 'utf-8')\n    message['From'] = Header(\" 监控 \", 'utf-8')\n    message['To'] = Header(\" 站长 \", 'utf-8')\n    message['Subject'] = Header(\" 告警 \", 'utf-8')\n    try:\n        smtpObj = smtplib.SMTP_SSL(\"smtp.exmail.qq.com\", 465)\n        smtpObj.login('service@anycodes.cn', '密码')\n        smtpObj.sendmail(sender, [to_user], message.as_string())\n    except smtplib.SMTPException as e:\n        logging.debug(e)
\n

完成模块编写，和上面的方法一样，进行项目部署。部署成功之后进行测试，测试可看到功能可用：

\n
    \n
  • 短信告警样式：
    • \n
\n

\"Serverless

\n
    \n
  • 企业微信告警样式：
    • \n
\n

\"Serverless

\n

总结

\n

通过本文的实践，希望读者可以了解到 Serverless 相关产品在运维行业中的基本应用，尤其是监控告警的基本使用方法和初步灵感。设计一个网站监控程序实际上是一个很初级的入门场景，希望大家可以将更多的监控告警功与 Serverless 技术进行结合，例如监控自己的 MySQL 压力情况、监控已有服务器的数据指标等，通过对这些指标的监控告警，不仅仅可以让管理者及时发现服务的潜在风险，也可以通过一些自动化流程实现项目的自动化运维。

\n

通过本场景实践，我们也可以对项目进行额外的优化或者应用在不同的领域以及场景中。例如，我们可以通过增加短信告警、微信告警、企业微信告警等多个维度，来确保相关人员可以及时收到告警信息；我们也可以通过监控某个小说网站、视频网站等，看到我们关注的小说或者视频的更新情况，便于追更等。

\n
\n
\n
\n
\n

传送门：

\n\n
\n

欢迎访问：Serverless 中文网，您可以在 最佳实践 里体验更多关于 Serverless 应用的开发！

","tableOfContents":""},"previousBlog":{"id":"162777c7-987a-5278-92ac-9887c8dc30a7","frontmatter":{"thumbnail":"https://img.serverlesscloud.cn/202049/1586443473383-1586438917%281%29_%E5%89%AF%E6%9C%AC.jpg","authors":["serverless 社区"],"categories":["meetup"],"date":"2020-04-11T00:00:00.000Z","title":"前端基于 Serverless 的开发探索 | 直播课","description":"本次直播将深入讲解 Serverless 给前端带来的变革、前端 Serverless 的发展方向，以及开发者如何基于 Serverless 获得成长，创造收益！","authorslink":["https://serverlesscloud.cn"],"translators":null,"translatorslink":null,"tags":["Serverless","Meetup"],"keywords":"Serverless;Front-end;","outdated":null},"wordCount":{"words":78,"sentences":16,"paragraphs":16},"fileAbsolutePath":"/opt/build/repo/content/blog/2020-04-11-serverless-front-end-development.md","fields":{"slug":"/blog/2020-04-11-serverless-front-end-development/","keywords":["serverless","云函数","Serverless","serverless","腾讯","serverlesscloud"]}},"nextBlog":{"id":"66fbf753-e21e-50af-9fb0-8d6ff3611176","frontmatter":{"thumbnail":"https://img.serverlesscloud.cn/2020522/1590170625843-%E4%BC%81%E4%B8%9A%E5%BE%AE%E4%BF%A1%E6%88%AA%E5%9B%BE_15901706165494.png","authors":["galenye"],"categories":["user-stories"],"date":"2020-04-09T00:00:00.000Z","title":"利用 Serverless，实现 COS & CDN Combo Handler","description":"小 S 维护的一个前端系统，单个页面中有数个没有依赖关系的 js, css 需要加载，此时浏览器会分别去请求对应的文件。此时小 S 收到 Leader 给的一个任务：优化前端的静态资源请求，尽量做合并。","authorslink":["https://cloud.tencent.com/developer/article/1610316"],"translators":null,"translatorslink":null,"tags":["Serverless","对象存储"],"keywords":"Serverless,COS,CDN","outdated":true},"wordCount":{"words":367,"sentences":52,"paragraphs":49},"fileAbsolutePath":"/opt/build/repo/content/blog/2020-04-09-serverless-combo-handler.md","fields":{"slug":"/blog/2020-04-09-serverless-combo-handler/","keywords":["java","serverless","combo","cdn","Serverless"]}},"recommendBlogs":{"edges":[{"node":{"id":"665f9ce2-4451-59fd-bf98-1861789d3b3b","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/Serverless_logo.png","authors":["AndreaPasswater"],"categories":["guides-and-tutorials","engineering-culture"],"date":"2018-03-19T00:00:00.000Z","title":"如何为无服务器开放源代码项目做贡献","description":"想要为无服务器开放源代码项目做贡献？您可以遵循下面的指南。","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":96,"sentences":36,"paragraphs":36},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-03-19-how-contribute-to-serverless-open-source.md","fields":{"slug":"/blog/2018-03-19-how-contribute-to-serverless-open-source/","keywords":["serverless","无服务器","serverless","github","插件","服务器","贡献","示例","blog","contribute"]}}},{"node":{"id":"a3e92579-65c3-5159-937c-32d18c5df7d7","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/why-not/why-not-header.png","authors":["AndreaPasswater"],"categories":["guides-and-tutorials","operations-and-observability","engineering-culture"],"date":"2018-03-21T00:00:00.000Z","title":"不适合选择无服务器的情境及原因","description":"无服务器既有优点也有缺点。那么，哪些情境下不适合选择无服务器？原因又是什么呢？","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":163,"sentences":43,"paragraphs":43},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-03-21-when-why-not-use-serverless.md","fields":{"slug":"/blog/2018-03-21-when-why-not-use-serverless/","keywords":["faas","react","serverless","spa","无服务器","无服务器函数","无服务器架构","无服务器开发","服务器","twitter","serverless","blockquote","lang","script","en"]}}},{"node":{"id":"6a16520b-7886-582e-9182-64e50712d486","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/vendor+choice/serverless-data-portability.jpg","authors":["NickGottlieb"],"categories":["engineering-culture","guides-and-tutorials"],"date":"2018-06-20T00:00:00.000Z","title":"浅谈无服务器、数据锁定和供应商选择","description":"供应商选择是如今 IT 领导者需要考虑的最重要事项，而这一点可利用数据可移植性来实现。","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":205,"sentences":33,"paragraphs":33},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-06-20-data-lockin-vendor-choice-portability.md","fields":{"slug":"/blog/2018-06-20-data-lockin-vendor-choice-portability/","keywords":["go","serverless","无服务器","无服务器架构","供应商","serverless","开发人员","数据","锁定","选择","服务"]}}},{"node":{"id":"94741abb-10ba-5db1-9756-cd1d573473fa","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/webstorm-ide/streamline-webstorm-serverless2.jpg","authors":["EslamHefnawy"],"categories":["guides-and-tutorials","engineering-culture"],"date":"2018-08-15T00:00:00.000Z","title":"如何使用 WebStorm 简化无服务器工作流程","description":"在本文中，我将和您分享如何使用 WebStorm 进行无服务器特定的 IDE 设置以及如何利用它来极大地加快无服务器工作流程。","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":234,"sentences":54,"paragraphs":54},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-08-15-streamline-serverless-workflow-webstorm.md","fields":{"slug":"/blog/2018-08-15-streamline-serverless-workflow-webstorm/","keywords":["nodejs","serverless","无服务器","无服务器开发","serverless","WebStorm","webstorm","服务器","blog","assets"]}}},{"node":{"id":"713a0563-4bf9-5721-bacb-3b4ef609fe4a","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/camp-fire/camp-fire-housing-thumb.jpg","authors":["EricWyne"],"categories":["guides-and-tutorials","user-stories"],"date":"2018-12-05T00:00:00.000Z","title":"Serverless Twitter 机器人帮助为坎普山火受灾者安置住房","description":"加利福尼亚州的坎普山火致使数千人流离失所，为此，我构建了一个简单的 Serverless Twitter 机器人来帮助将受灾者安置在临时住房！","authorslink":["https://serverless.com/author/ericwyne/"],"translators":["Aceyclee"],"translatorslink":["zhihu.com/people/Aceyclee"],"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":157,"sentences":26,"paragraphs":26},"fileAbsolutePath":"/opt/build/repo/content/blog/2018-12-05-serverless-twitter-camp-fire.md","fields":{"slug":"/blog/2018-12-05-serverless-twitter-camp-fire/","keywords":["serverless","无服务器","云函数","Serverless","org","住房","Twitter","函数","受灾","机器人","山火"]}}},{"node":{"id":"17c972d9-0583-51f6-9d5d-c2ba5f21b6a3","frontmatter":{"thumbnail":"https://img.serverlesscloud.cn/20191227/1577409288454-v2-577c2b21d600e3ea07f156f3e9d2d6b8_1200x500.jpg","authors":["Alfred Huang"],"categories":["guides-and-tutorials"],"date":"2019-08-21T00:00:00.000Z","title":"Serverless 的运行原理与组件架构","description":"本文重点探讨下开发者使用 Serverless 时经常遇到的一些问题，以及如何解决","authorslink":["https://zhuanlan.zhihu.com/ServerlessGo"],"translators":null,"translatorslink":null,"tags":["运行原理","serverless"],"keywords":"Serverless 运行原理,Serverless 组件架构","outdated":null},"wordCount":{"words":236,"sentences":33,"paragraphs":33},"fileAbsolutePath":"/opt/build/repo/content/blog/2019-08-21-serverless-operation-architecture.md","fields":{"slug":"/blog/2019-08-21-serverless-operation-architecture/","keywords":["koa","serverless","云函数","Serverless","用户","函数","请求","实例","形态","业务","serverlesscloud"]}}},{"node":{"id":"ae4fd2f8-515c-5aec-b584-38427ef33f7e","frontmatter":{"thumbnail":"https://img.serverlesscloud.cn/2020114/1578989800047-part-00492-780.jpg","authors":["Anycodes"],"categories":["guides-and-tutorials","user-stories"],"date":"2019-09-16T00:00:00.000Z","title":"突破传统 OJ 瓶颈，「判题姬」接入云函数","description":"通过 Serverless 实现在线编程","authorslink":["https://www.zhihu.com/people/liuyu-43-97"],"translators":null,"translatorslink":null,"tags":["在线编程","云函数"],"keywords":"Serverless 在线编程,Serverless OJ","outdated":null},"wordCount":{"words":169,"sentences":30,"paragraphs":30},"fileAbsolutePath":"/opt/build/repo/content/blog/2019-09-16-online-Judge.md","fields":{"slug":"/blog/2019-09-16-online-Judge/","keywords":["python","serverless","云函数","代码","函数","serverless"]}}},{"node":{"id":"545ab3d2-e14e-5cc2-8548-0e863eac942b","frontmatter":{"thumbnail":"https://s3-us-west-2.amazonaws.com/assets.blog.serverless.com/2019-10-deployment-best-practices/safeguard-header.png","authors":["FernandoMedinaCorey"],"categories":["guides-and-tutorials"],"date":"2019-10-14T00:00:00.000Z","title":"无服务器部署最佳实践","description":"了解部署无服务器应用时的一些最佳实践。","authorslink":null,"translators":null,"translatorslink":null,"tags":null,"keywords":null,"outdated":null},"wordCount":{"words":221,"sentences":46,"paragraphs":46},"fileAbsolutePath":"/opt/build/repo/content/blog/2019-10-14-serverless-deployment-best-practices.md","fields":{"slug":"/blog/2019-10-14-serverless-deployment-best-practices/","keywords":["serverless","无服务器","serverless","部署","服务器","开发人员","应用","安全措施","使用","函数"]}}}],"totalCount":31}},"pageContext":{"isCreatedByStatefulCreatePages":false,"blogId":"44ad21a9-00a3-592c-83c1-696af478c55f","previousBlogId":"162777c7-987a-5278-92ac-9887c8dc30a7","nextBlogId":"66fbf753-e21e-50af-9fb0-8d6ff3611176","categories":["guides-and-tutorials","operations-and-observability"]}}}