# Project Daily Tasks

**AIM :**

* Start learning from scratch and implement whatever learned on everyday with practical hands-on. Integrate all DevOps tools for a single project i.e; Ecommerce- Microservices project

## **Project Details : E-Commerce Microservices Platform** <a href="#project-details-e-commerce-microservices-platform" id="project-details-e-commerce-microservices-platform"></a>

&#x20;

The e-commerce platform is a microservices-based application with four core services (User, Product, Order, Recommendation) deployed on AWS using Kubernetes. It’s supported by a CI/CD pipeline, monitoring tools, a database, and security measures, all optimized for scalability, elasticity, and reliability. Here’s the breakdown:

1. **Microservices**:
   * **User Service**: Java/Spring Boot, handles user data (e.g., /users endpoint).
   * **Product Service**: Node.js, manages product catalog (e.g., /products).
   * **Order Service**: Python/Flask, processes orders (e.g., /orders).
   * **Recommend Service**: Go, provides recommendations (e.g., /recommend).
   * Communication: REST APIs between services.
2. **Infrastructure**:
   * **AWS EC2**: Single t2.micro instance (free tier) hosting a Kubernetes cluster via kubeadm.
   * **AWS RDS**: PostgreSQL (free tier) for persistent storage (User Service data).
   * **Networking**: Kubernetes Ingress for routing, DuckDNS for domain (ecomm.duckdns.org), HTTPS via Let’s Encrypt.
3. **CI/CD**:
   * **GitHub**: Code repository (github.com/yourusername/ecomm-devops).
   * **GitHub Actions**: Automates build, test, and deploy to Kubernetes.
   * **Docker**: Containerizes each microservice, pushed to Docker Hub.
4. **Monitoring & Observability**:
   * **Prometheus**: Metrics collection (e.g., CPU, request rates).
   * **Grafana**: Dashboards for visualization.
   * **ELK Stack**: Centralized logging (Elasticsearch, Logstash, Kibana).
   * **AWS CloudWatch**: Basic AWS metrics (augments Prometheus).
5. **Security**:
   * **Vault**: Manages secrets (e.g., API keys).
   * **Kubernetes RBAC**: Role-based access control.
   * **Network Policies**: Restricts service communication.
   * **HTTPS**: Secured with Let’s Encrypt certificates.
6. **Project Tracking**:
   * **Jira**: Manages tasks, epics, and sprints (e.g., ECOMM-8 for User Service).

**About Project :**

You’ll build a production-ready e-commerce platform with multiple microservices:

* **User Service** (Java): Manages user registration, authentication, and profiles.
* **Product Service** (Node.js): Handles product catalog and inventory.
* **Order Service** (Python): Processes orders and payments.
* **Recommendation Service** (Go): Provides product recommendations based on user activity.

This system will run on Linux servers, use modern DevOps tools, and be deployed on Kubernetes in a production-like environment

&#x20;

<figure><img src="/files/lUZXBjBtGbC48tbNmECz" alt=""><figcaption></figcaption></figure>

**Prerequisites**

* Basic familiarity with Linux, programming (Go, Python, Java, Node.js), and Git.
* A Linux VM (e.g., Ubuntu) or cloud instance (e.g., AWS EC2) for hands-on practice.
* Install: Git, Docker, VS Code, and a Jira instance (self-hosted or Atlassian Cloud free tier).

&#x20;

#### Tools & Concepts Covered <a href="#tools-and-concepts-covered" id="tools-and-concepts-covered"></a>

1. **Linux**: Server management, shell scripting.
2. **Git/GitHub**: Version control, CI/CD workflows.
3. **Jenkins/GitHub Actions**: CI/CD pipelines.
4. **Docker**: Containerization.
5. **SonarQube**: Code quality.
6. **Trivy/OWASP**: Security scanning.
7. **Testing**: Unit, integration, load testing.
8. **Kubernetes**: Orchestration.
9. **Terraform**: Infrastructure as Code.
10. **Ansible**: Configuration management.
11. **Vault**: Secret management.
12. **Prometheus/Grafana**: Monitoring.
13. **ELK**: Logging.
14. **Jira**: Project tracking.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://charan-techjourney.gitbook.io/charan-techjournal/50-days-of-devops-ecommerce-microservices/project-daily-tasks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.