Ems 161 implement admin user messaging system

README.md

@@ -72,15 +72,12 @@ The EMS follows a **3-tier architecture** for scalability and maintainability:
 
 ## 🏗️ Services Created
 
-- **auth-service**: NestJS microservice with health endpoints
-- **user-service**: NestJS microservice with health endpoints
-- **event-service**: NestJS microservice with health endpoints
-- **booking-service**: NestJS microservice with health endpoints
-- **ticketing-service**: NestJS microservice with health endpoints
-- **speaker-service**: NestJS microservice with health endpoints
-- **feedback-service**: NestJS microservice with health endpoints
-- **notification-service**: NestJS microservice with health endpoints
-- **reporting-analytics-service**: NestJS microservice with health endpoints
+- **auth-service**: Node.js microservice with health endpoints
+- **event-service**: Node.js microservice with health endpoints
+- **booking-service**: Node.js microservice with health endpoints
+- **speaker-service**: Node.js microservice with health endpoints
+- **feedback-service**: Node.js microservice with health endpoints
+- **notification-service**: Node.js microservice with health endpoints
 
 ## 🚀 Running Services
 
@@ -98,14 +95,11 @@ docker-compose up -d
 ```
 ├── ems-client/           # Next.js frontend with health endpoint
 ├── ems-gateway/          # NGINX configuration
-└── ems-services/         # NestJS microservices
+└── ems-services/         # Node.js microservices
     ├── auth-service/
-    ├── user-service/
     ├── event-service/
     ├── booking-service/
-    ├── ticketing-service/
     ├── speaker-service/
     ├── feedback-service/
-    ├── notification-service/
-    └── reporting-analytics-service/
+    └── notification-service/
 ```

docker-compose.test-db.yaml

@@ -15,6 +15,10 @@ services:
       interval: 10s
       timeout: 5s
       retries: 5
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
 volumes:
   ems-db-test-data:

docker-compose.yaml

@@ -12,6 +12,10 @@ services:
       ./ems-client/.env.production
     networks:
       - event-net
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   ems-gateway:
     build:
@@ -31,6 +35,10 @@ services:
       - booking-service
       - speaker-service
       - notification-service
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   #########################################
   #   BACKEND MICROSERVICES
@@ -52,6 +60,10 @@ services:
         condition: service_healthy
       rabbitmq:
         condition: service_started
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   event-service:
     <<: *base-service
@@ -74,6 +86,10 @@ services:
         condition: service_started
       auth-service:
         condition: service_started
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   booking-service:
     <<: *base-service
@@ -92,6 +108,10 @@ services:
         condition: service_healthy
       rabbitmq:
         condition: service_started
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   feedback-service:
     <<: *base-service
@@ -103,13 +123,19 @@ services:
     container_name: feedback-service
     env_file:
       ./ems-services/feedback-service/.env.production
+    environment:
+      - JWT_SECRET=supersecretkey
     networks:
       - event-net
     depends_on:
       feedback-service-db:
         condition: service_healthy
       rabbitmq:
         condition: service_started
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   notification-service:
     build:
@@ -123,6 +149,10 @@ services:
     depends_on:
       rabbitmq:
         condition: service_started
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   speaker-service:
     <<: *base-service
@@ -146,6 +176,10 @@ services:
         condition: service_healthy
       rabbitmq:
         condition: service_started
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   #########################################
   #   DATABASES FOR MICROSERVICES
@@ -167,6 +201,10 @@ services:
       interval: 10s
       timeout: 5s
       retries: 5
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   event-service-db:
     <<: *base-service-db
@@ -177,6 +215,10 @@ services:
       - POSTGRES_DB=event_db
     volumes:
       - event-service-data:/var/lib/postgresql/data
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   booking-service-db:
     <<: *base-service-db
@@ -187,6 +229,10 @@ services:
       - POSTGRES_DB=booking_db
     volumes:
       - booking-service-data:/var/lib/postgresql/data
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   feedback-service-db:
     <<: *base-service-db
@@ -197,6 +243,10 @@ services:
       - POSTGRES_DB=feedback_db
     volumes:
       - feedback-service-data:/var/lib/postgresql/data
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   speaker-service-db:
     <<: *base-service-db
@@ -207,6 +257,10 @@ services:
       - POSTGRES_DB=speaker_db
     volumes:
       - speaker-service-data:/var/lib/postgresql/data
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
   #########################################
   #   INFRASTRUCTURE SERVICES
@@ -231,6 +285,10 @@ services:
       timeout: 10s
       retries: 5
       start_period: 20s # Give RabbitMQ time to start up before checking
+    deploy:
+      resources:
+        limits:
+          memory: 512M
 
 # This section defines the custom network for our services to communicate.
 networks: