feat: merged with main

Dockerfile

@@ -0,0 +1,15 @@
+FROM node:latest
+
+# Create app directory
+WORKDIR /usr/src/app
+
+# Install app dependencies
+
+# If you also need http-server globally
+RUN npm install -g http-server
+
+# Bundle app source
+COPY . .
+
+EXPOSE 8080
+CMD ["http-server", "-p 8080"]

docs/IndividualServices/analytics_service.txt

@@ -0,0 +1,12 @@
+1. Receive data from database
+2. Calculate data:    
+    a) User Count 
+    b) Movies Count 
+    c) Rating Count 
+    d) Total data size 
+    e) "Hot" movies -> movies that received most ratings during last 
+        week 
+    f) System logs (keeps tracks of all messages exchanged by all services)
+        1. timestamp (when was a message send)
+        2. Message raw data 
+3. Send requests to frondend upon request 

docs/toDos/deployment_script.txt

@@ -0,0 +1,25 @@
+One script upon being ran should deploy the entire solution to some 
+cloud service
+
+It should:
+1. Build everything 
+2. Connect to cloud service (Azure?)
+3. Send the data 
+
+After it will be run website should be accessible under some address 
+    (cloud service should provide this address?)
+
+Decide:
+    What cloud service? (Azure?) Requirements:
+        a. Free (https://github.com/cloudcommunity/Cloud-Free-Tier-Comparison)
+        b. Popular 
+            AWS:
+                +   Most popular 
+                +   "Always" free
+                +   AWS CDK available
+            Azure 
+                -Microsoft
+            Google Cloud 
+                +We have google accounts anyway
+    What technology for script (Ansible?)
+

docs/toDos/monitoring_service.txt

@@ -0,0 +1,12 @@
+Monitoring service 
+Monitoring service should keep track of all communication 
+send between all services 
+Store logs with:
+1. timestamp (when was a message send)
+2. Message raw data 
+
+To decide: 
+    What to use for Monitoring service? 
+    Maybe cloud service will provide us with functioning one?
+    Maybe deployment tool already has one?
+