IIT Patna Projects is the central organization for all repositories created during the Executive M.Tech in Cloud Computing program at IIT Patna. Course projects, mini-projects, experiments, study material and research work are kept here under one consistent structure, instead of being scattered across personal accounts.

The organization exists to answer one question for every piece of work in it:

Does this system actually behave the way we say it does?

Cloud computing is easy to describe and harder to demonstrate. A system is only "scalable", "available" or "secure" if it can be shown with measurements, so each project here is expected to define its targets, test against them and report what happened, including what did not work.

1. Evidence over claims. Every quality attribute (availability, latency, scalability, recovery time) is stated as a measurable target and checked against real test results.

2. Reproducibility. Anyone should be able to rebuild an environment and rerun an experiment from the repository alone, using containers and infrastructure as code.

3. Realistic workloads. Systems are exercised with traffic that resembles real usage (user journeys, bursts, sustained load, automated clients) rather than synthetic one-line requests.

4. Operate what you build. Monitoring, alerting and recovery procedures are part of the project, not an afterthought.

5. Responsible testing. Load and security tests target only systems owned by this organization, using synthetic data and accounts.

6. Cost awareness. Budgets and alerts are configured before deployment, capacity is kept minimal, and resources are removed once an experiment ends.

7. Honest reporting. Failed experiments, missed targets and limitations are documented alongside successes.

Each repository follows the same lifecycle, so results are comparable across projects.

flowchart LR
    A[Define<br/>requirements and<br/>measurable targets] --> B[Build<br/>application and<br/>infrastructure]
    B --> C[Stress<br/>realistic and<br/>extreme workloads]
    C --> D[Observe<br/>metrics, logs,<br/>alerts]
    D --> E[Evaluate<br/>against targets]
    E --> F[Document<br/>findings and<br/>lessons]
    E -. iterate .-> B

Work in this organization spans the layers of a modern cloud system.

flowchart TB
    subgraph L1[Workload and Traffic]
        W1[Load generation]
        W2[User-journey simulation]
        W3[Traffic classification]
    end
    subgraph L2[Application and Delivery]
        A1[Application services]
        A2[Containers]
        A3[CI/CD pipelines]
    end
    subgraph L3[Cloud Infrastructure]
        I1[Compute and networking]
        I2[Load balancing]
        I3[Auto scaling]
        I4[Managed data stores]
    end
    subgraph L4[Operations and Assurance]
        O1[Monitoring and alerting]
        O2[SLA and TTR measurement]
        O3[Security controls]
        O4[Cost analysis]
    end
    L1 --> L2 --> L3 --> L4

This index is updated whenever a repository is added or changes state.

Status definitions

Repository types: Project end-to-end builds, Assignment course deliverables, Experiment benchmarks and studies, Notes study material, Tooling reusable scripts and templates, Research write-ups and reviews.

Every repository is expected to contain the following, so any project can be understood and run in minutes.

repository/
├── README.md        Purpose, architecture, setup, results
├── LICENSE          Usage terms
├── docs/            Design decisions, test plans, reports
├── infrastructure/  Infrastructure as code
├── tests/           Functional and workload tests
├── .env.example     Required configuration, with no secrets
└── .gitignore

Tools are chosen to solve a demonstrated problem, not for novelty.

Priyanshu Kumar Sharma is a B.Tech Information Technology graduate and a first-year Executive M.Tech (Cloud Computing) student at IIT Patna, based in Pune. He works across cloud technology, information security and research-driven systems, with industry experience in CI/CD and containerization and research experience in serverless computing and FaaS benchmarking at IIT Ropar.

Feedback, corrections and ideas are welcome.

1. Open an issue in the relevant repository describing the suggestion or problem.
2. For changes, fork the repository and create a branch.
3. Submit a pull request that explains what changed and how it was tested.