SrujanScale

Docker Desktop containers
Green GitHub Actions

🚀 Inspiration

In modern software engineering, writing code is only half the battle. True reliability happens in the infrastructure. I was inspired to move beyond basic local development and explore the "Gold Standard" of Site Reliability Engineering (SRE): building systems that don't just run, but scale, self-heal, and remain observable under pressure.

🏗️ How I Built It

I approached SrujanScale using a tiered production engineering strategy to ensure total system health:

Bronze (Reliability): I implemented a GitHub Actions CI pipeline. On every push, the system automatically spins up a PostgreSQL service, installs dependencies, and runs a rigorous test suite to ensure zero regressions.
Silver (Scalability): I containerized the entire stack using Docker. By leveraging Docker Compose, I implemented horizontal scaling with three replicas of the web server. This allows the application to handle high-traffic loads by distributing requests across multiple container instances.
Gold (Resilience): I applied Chaos Engineering principles. I engineered the system to be resilient against dependency failures. By testing "hard failure" scenarios—like manually killing the database—I verified that the infrastructure remains observable and can self-heal instantly once the service recovers.

🧠 Challenges I Faced

The biggest hurdle was Container Networking. Getting isolated Docker containers to "discover" each other using service names instead of local IP addresses required a deep dive into virtual networking. I also had to debug complex YAML mapping errors and port allocation conflicts when scaling to multiple replicas on a single host.

🎓 What I Learned

I learned the true power of Infrastructure as Code (IaC). I now understand how to manage environment variables across different stages of a pipeline, how to use container health checks to prevent "race conditions," and how to analyze real-time logs to debug a distributed system.

🏆 What's Next for SrujanScale

Next, I plan to implement a proper Reverse Proxy using Nginx to handle true load balancing across the replicas and explore Kubernetes to move from local orchestration to cloud-scale management.