Chapter 1: The Beginning of the Journey

A few years back, I set out on a personal endeavor to build my own website. It started as a simple static React application, managed in a GitHub repository and hosted on GitHub Pages. This straightforward approach worked well for me at the time. However, I soon faced a challenge: all of my blog links were hardcoded, making it necessary to push to GitHub every time I wanted to add a new post. The remedy seemed clear—integrating a database, possibly MongoDB, to automate this process.

In addition to my blog, I also wanted to feature my various projects. As these projects grew, I recognized the need for a more substantial backend. Instead of relying on a single, cumbersome Backend-for-Frontend (BFF), I became interested in utilizing microservices designed for specific functions. For example, my future explorations into machine learning would necessitate a Python stack, and I was eager to try out different frameworks—perhaps even experimenting with Vue for certain UI components, diverging from my typical React usage.

Initially, I thought about adding features incrementally—a database here, a Python backend there. But as I explored further, I understood that this patchwork approach would only result in a convoluted tech stack. At that pivotal moment, I decided to prioritize being an engineer over my instinct to quickly resolve immediate challenges.

A tech stack should ideally be structured to achieve specific goals, grounded in particular assumptions. When we try to implement features that contradict those foundational assumptions, we often resort to improvised solutions that rarely lead to success. As Sun Tzu wisely stated:

> "Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before defeat."

Consequently, I am now on a mission to evolve my site into a dynamic, scalable, and robust web application. This journey will leverage open-source technologies and established cloud services, emphasizing containerization, continuous deployment, and Infrastructure as Code (IaC). My aim is to create a fully automated pipeline that deploys a highly available, scalable, and fault-tolerant architecture, complete with comprehensive monitoring and logging.

Why Focus on Scalability and Resilience?

While this is my personal website, I don't expect it to attract a significant amount of traffic. In reality, a single instance of my deployable services should suffice, and I might even get by with just one host. This pursuit is more about personal growth than necessity. I have experience in building scalable stacks using AWS but lack familiarity with open-source tools. Thus, this endeavor serves as a valuable opportunity for my learning.

Why Document This Journey?

I strongly advocate for software documentation, and blogging allows me to do so while narrating my experience. Humans are inherently storytellers, echoing our ancestral tradition of sharing tales around the fire—a spark that perhaps ignited civilization itself.

As a software developer, I appreciate the importance of thorough documentation. The writer in me seeks to infuse narrative elements into it, creating a blog that fulfills both purposes.

What Should You Expect?

The roadmap I plan to outline, if executed effectively, will serve as a comprehensive guide for building and deploying a web application in a real-world context. I will utilize various technologies like MERN (MongoDB, Express, React, Node), Docker, Kubernetes, Helm, GitHub Actions, Terraform, and more. While many tutorials tackle these subjects in isolation, there is a gap for an end-to-end guide—from a basic web app to a fully developed tech stack capable of adapting to increasing traffic and evolving feature sets.

As I progress through each step of this roadmap, I will publish in-depth blogs detailing my findings. I believe this series will be beneficial for both seasoned engineers and aspiring developers, providing practical insights that can enhance your daily work and possibly aid in future job interviews. Whether you're keen to acquire these skills or simply interested in the narrative, this blog could be worth your time!

Now, let's delve into the actual roadmap.

The Roadmap

1. Current State
   • My current setup is a static React site, version-controlled in a GitHub repo and deployed on GitHub Pages.
2. Containerization
   • Implementing containerization will simplify backend integration and streamline development processes.
   • Technology Choice:
     • Docker: a widely adopted solution with a robust ecosystem.
     • Possible Alternatives: Podman

3. Backend API Development
   • The backend API will facilitate dynamic content management, paving the way for effective database integration.
   • This first API will be a simple CRUD (Create — Read — Update — Delete) RESTful API for managing blog posts.
   • Technology Choice:
     • Express.js: I'm eager to learn the MERN stack!
     • Possible Alternatives: Spring Boot
4. Database Integration
   • Adding a database will provide persistent data storage, eliminating the need for hardcoded blog posts.
   • Technology Choice:
     • NoSQL: I need low-latency lookups and a flexible datastore.
     • MongoDB: It's a free/affordable option that scales well.
     • Possible Alternatives: DynamoDB
5. Container Orchestration
   • This will tackle the complexities of manual container scaling and management, allowing for systematic expansion of the stack.
   • Core Technology Choice:
     • Kubernetes: Ideal for scalable and self-healing container orchestration.
     • Possible Alternatives: Docker Swarm

• Orchestration Helper Technology Choice:

  • Helm: Streamlines Kubernetes application deployments.
  • Possible Alternatives: Kustomize

6. Continuous Deployment Pipeline
   • A comprehensive CI/CD pipeline will automate the build, test, and deployment processes, enhancing software delivery efficiency.
   • Technology Choice:
     • GitHub Actions: Offers seamless CI/CD integration within GitHub repositories.
     • Possible Alternatives: Jenkins
7. Cloud Services Integration
   • Leveraging reliable cloud services will enhance storage and messaging capabilities.
   • Technology Choice:
     • AWS: A comprehensive suite of scalable services.
     • Possible Alternatives: Azure, Google Cloud Platform
8. Infrastructure as Code (IaC)
   • IaC will streamline cloud infrastructure management, ensuring consistency and enhancing security.
   • Technology Choice:
     • Terraform: Excellent for managing infrastructure consistently across providers.
     • Possible Alternatives: AWS CDK
9. Monitoring and Logging
   • This will provide insights into application performance and health, completing the transition to a production-ready application.
   • Technology Choice:
     • Prometheus and Grafana: Cost-effective solutions for real-time monitoring and visualization.
     • ELK Stack: Essential for operational visibility.
     • Possible Alternatives: AWS CloudWatch, AWS OpenSearch

Concluding Thoughts

This roadmap is organized into high-level steps, each indicating a significant change and involving multiple tasks. Given that this is a solo passion project, delving into minute details may not be necessary. For those interested, code commits will be available for review, and I'll associate each commit with a corresponding GitHub issue for useful insights.

The technologies chosen in this roadmap reflect a mix of cost, usability, and my current knowledge. As I learn more, I might switch to different technologies or modify certain steps. I will ensure to keep this blog updated for accuracy and consistency.

Thank you for joining me on this journey. I look forward to your feedback! If you think the roadmap needs adjustments or if you have any questions, please feel free to reach out. Engaging in thoughtful discussions about technology is one of life's great joys.

For more insights on coding and software development, consider following me on Medium for updates directly to your inbox! 😊

Chapter 2: Learning from the Experts

In this chapter, we will explore valuable resources that can help shape our understanding of IT strategy and technology roadmaps.

The first video discusses how to create an effective IT strategy and map out a technology roadmap, providing insights that will be crucial as we navigate our own development journey.

The second video focuses on how non-technical founders can create an app development roadmap, offering perspectives that can benefit anyone looking to build a web application.