One post tagged with "Docusaurus"

I have migrated the website architecture from Next.js to the open-source Docusaurus, and simultaneously transitioned the server from the previous service+CDN architecture to a fully Serverless environment.

1. About Migrating to Docusaurus​

Currently, my development speed alone is not sufficient to support the platform I envision. Therefore, I have decided to invest more resources into developing what I consider to be more critical and exciting features. This may, of course, result in some inconveniences, such as the inability to perform certain advanced web operations that were possible before. However, this will not hinder me from continuing to use the previous design and my user interface (UI) design. Additionally, my development work will continue, including the design of components and icons.

If you are not a professional developer and are not familiar with what Docusaurus is:

• Docusaurus is a comprehensive page design tool that allows me (as a user) to fully focus on content creation without worrying about various formatting issues. Of course, if I need special formatting or additional functionality, customization can be done on top of it.
• The biggest benefit, in my opinion, is that Docusaurus is based on the open-source community, so I can always get new features provided by the community, such as new buttons, input fields, etc., without spending too much time on it.

2. About Abandoning Traditional Service Architecture​

One of the most significant changes in this update is my abandonment of the previous traditional service architecture in favor of a fully Serverless architecture. While I could list many theoretical reasons for adopting Serverless, the following are the ones that truly convinced me:

1. Cost Savings​

Transitioning from a traditional server architecture to a microservices architecture resulted in a reduction of approximately 60% in my actual expenditure for the same computing capacity.

2. Streamlined Operations​

There is almost no need for tedious operational work.

• Firstly, load balancing: While we still need to consider load balancing at the CDN level, we no longer have to worry about load balancing at the server level. And if it happens to involve stateless services, we can achieve load balancing at the CDN level, significantly reducing maintenance burdens and costs.
• Next is server-related issues: including networking, system, security, and system updates. Although these operational issues still arise when using Self Host Serverless, there is no longer the worry of an entire server crashing due to the failure of one service, thanks to a simple and cost-effective load balancing solution. Of course, for well-funded enterprises that have always used dedicated load balancing, this may not be an issue.
• Then comes deployment: Traditional deployment methods usually involve shutting down services, copying files, and restarting. However, with the help of container technology and Serverless technology, these processes are no longer required. Combined with modern automated deployment workflows, most of my websites (about 90%) are now automated deployments.

3. Security​

This is quite interesting. While it cannot be said that Serverless is necessarily more secure, at least the issues regarding system security have become more abstract. Let me briefly outline the timeline of security evolution:

• 2020: Logging into servers via passwords over public networks, with databases also hosted on servers.
• 2021: Logging into servers via certificates, and placing the database on a separate server isolated from the internet.
• 2022: Logging into servers via certificates, with no dedicated server for the database.
• 2023: All public services no longer rely on dedicated servers.