<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Backend on Mi&amp;Bee Blog</title><link>/en/categories/backend/</link><description>Recent content in Backend on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Wed, 30 Jan 2019 00:00:00 +0000</lastBuildDate><atom:link href="/en/categories/backend/rss.xml" rel="self" type="application/rss+xml"/><item><title>Implementing a Lightweight File Backup System Based on OpenResty</title><link>/en/archives/06-openresty-backup-system/</link><pubDate>Wed, 30 Jan 2019 00:00:00 +0000</pubDate><guid>/en/archives/06-openresty-backup-system/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;There are tools like &lt;strong&gt;filebeat&lt;/strong&gt; for log collection, open-source cloud drives like &lt;strong&gt;seafile&lt;/strong&gt;, and simple distributed file systems like &lt;strong&gt;FastDFS&lt;/strong&gt;, among others. However, the remote backup logs of a certain enterprise SaaS platform still rely on traditional compressed file scp transfers to backup storage.&lt;/p&gt;
&lt;p&gt;Since filebeat&amp;rsquo;s log collection completeness is debatable, open-source cloud drives have cluttered features that are not conducive to management, distributed file systems&amp;rsquo; internal storage logic is not well-suited for the backup log management of the enterprise SaaS platform, and scp transfers pose security risks with private keys deployed on servers, we leveraged OpenResty&amp;rsquo;s features to implement a simple file backup API interface using Lua.&lt;/p&gt;</description></item></channel></rss>