Why I Moved This Blog Away from MongoDB

For a personal portfolio, a database is not always necessary. A database is useful when posts need to be created through an admin dashboard, edited by multiple users, or updated frequently from an application interface.

But for a portfolio blog, static content is often better.

Why static works well

A static blog stores posts directly in the codebase. That means the content lives in GitHub, deploys through Vercel, and does not require a separate database service.

The benefits are simple:

• fewer deployment errors
• no database credentials to manage
• faster page rendering
• easier version control
• simpler long-term maintenance

Tradeoff

The tradeoff is that new posts require a Git commit. For my use case, that is acceptable because blog posts are part of the portfolio itself.

Final decision

I chose a static blog because it keeps the site lightweight and reliable. If I need a full CMS later, I can add one. For now, GitHub plus Vercel is enough.