fix: remove realm leftovers

cdsp/information-layer/README.md

@@ -1,68 +1,81 @@
 # Information Layer Server (IL)
 
-The information layer Server (IL) is responsible for providing a raw data access [API](#api) (read, write, subscribe).
+The Information Layer Server (IL) is responsible for providing a raw data access [API](#api) (read, write, subscribe).
 Its intention is to abstract the underlying data storage database technology. It is written in Typescript.
 
-Clients can interact with it using websockets and JSON payload.
-
+Clients can interact with it using web sockets and JSON payload.
 
 The IL consists of two logical components:
+
 - database handler: Interaction with the chosen database, configurable
 - router: API provider that connects to the database handler
 
 ```mermaid
 flowchart LR
     client <--> router
     router <--> handlers
-    handlers <--> realm_handler
     handlers <--> iotdb_handler
     realm_handler <--> realmdb
     iotdb_handler <--> iotdb
 ```
 
-# Information Layer Server - Hello World Setup 
+# Information Layer Server - Hello World Setup
 
 ### Build the typescript application natively
 
 Make sure all libraries are installed
+
 ```bash
 npm install
 ```
+
 Build the application
+
 ```bash
 npm run build
 ```
+
 Run the unit tests
+
 ```bash
 npx jest
 ```
+
 or
+
 ```bash
 npx jest --verbose
 ```
 
-## Run IL with backend option 1: Timeseries Data Server IoTDB
+## Run with IoTDB backend option
 
 ### Start the database
 
 Start the db:
+
 ```bash
 docker run -d --rm --name iotdb-service -p 6667:6667 -p 9003:9003 apache/iotdb:latest
 ```
+
 if you plan on running the Information Layer also with docker, IotDB and IL container need to be in the same network:
+
 ```bash
 docker network create cdsp-net
 docker run -d --rm --name iotdb-service --network cdsp-net -p 6667:6667 -p 9003:9003 apache/iotdb:latest
 ```
 
 Connect to it via cli to create or view the data (optional):
+
 ```bash
 docker exec -it iotdb ./start-cli.sh -h 127.0.0.1 -p 6667 -u root -pw root
 ```
+
 Create a database (optional)
+
 ```bash
 create database root.Vehicles
 ```
+
 Create desired timeseries (optional)
 
 ```bash
@@ -73,10 +86,13 @@ create timeseries root.Vehicles.Vehicle_Speed WITH DATATYPE=FLOAT, ENCODING=RLE
 ### Start Information Layer Server
 
 Build the Information Layer image
+
 ```bash
 docker build -t information-layer .
 ```
+
 Run IL
+
 ```bash
 # Docker
 docker run --rm --name information-layer --network cdsp-net -p 8080:8080 -e HANDLER_TYPE=iotdb -e IOTDB_HOST=iotdb-service information-layer
@@ -85,38 +101,6 @@ npm install
 HANDLER_TYPE=iotdb IOTDB_HOST=localhost npm start
 ```
 
-## Run IL with backend option 2: Document Data Service RealmDB
-
-
-### Prepare cloud
-
-- Ensure that in your [ATLAS cloud](https://cloud.mongodb.com/) app there is a vehicle _document_ with an
-  `Vehicle_VehicleIdentification_VIN` in a collection named _`Vehicles`_.
-- Ensure that this document as well contains VSS data. Here you can see the data supported in this repository for a vehicle document within
-  _Vehicles_ that should be reflected in ATLAS:
-
-```
-_id: "<SOME_STRING>" (String)
-Vehicle_Speed: <SOME_DOUBLE> (Double)
-Vehicle_TraveledDistance: "<SOME_DOUBLE>" (Double)
-```
-
-### Start Information Layer Server
-
-Build the Information Layer image
-```bash
-docker build -t information-layer .
-```
-
-Run the Information Layer
-```bash
-# Docker
-docker run -d --rm --name information-layer --network cdsp-net -p 8080:8080 -e HANDLER_TYPE=realmdb -e VERSION_REALMDB_SCHEMA=0 -e REALMDB_APP_ID=<YOUR-APP-ID> -e REALMDB_API_KEY=<YOUR-API-KEY> information-layer
-# OR natively
-npm install
-HANDLER_TYPE=realmdb VERSION_REALMDB_SCHEMA=0 REALM_APP_ID=<YOUR-APP-ID> REALM_API_KEY=<YOUR-API-KEY> npm start
-```
-
 ## Usage
 
 See [api](#api) how to interact with the router.
@@ -130,6 +114,7 @@ The examples use [websocat](https://github.com/vi/websocat) and [jq](https://git
 ## Get
 
 Schema:
+
 ```yaml
 # only the root node provided to get all data points
 {
@@ -157,13 +142,15 @@ Schema:
 ```
 
 Example:
+
 ```bash
 echo '{"type": "get","instance": "VIN_123","schema": "Vehicle","path": "Speed","requestId": "123-456"}' | websocat ws://localhost:8080 -n1 | jq
 ```
 
 ## Set
 
 Schema:
+
 ```yaml
 # leaf node with single value in data
 {
@@ -201,68 +188,58 @@ Schema:
   "requestId": "235-183"
 }
 ```
+
 Example:
+
 ```bash
 echo '{"type": "set","path": "CurrentLocation.Latitude","instance": "VIN_123","schema": "Vehicle","data": 21}' | websocat ws://localhost:8080 -n1 | jq
 ```
+
 ```yaml
 {
   "type": "status",
   "code": 200,
   "message": "Successfully wrote data to database.",
-  "timestamp": {
-    "seconds": 1738613888,
-    "nanos": 143000000
-  }
+  "timestamp": { "seconds": 1738613888, "nanos": 143000000 },
 }
 ```
 
 ## Subscribe
 
 Schema:
+
 ```yaml
-{
-  "type": "subscribe",
-  "instance": "VIN_123",
-  "schema": "Vehicle"
-}
+{ "type": "subscribe", "instance": "VIN_123", "schema": "Vehicle" }
 ```
+
 ```bash
-echo '{"type": "subscribe", "instance": "VIN_123", "schema": "Vehicle"}' | websocat ws://localhost:8080 -n | jq 
+echo '{"type": "subscribe", "instance": "VIN_123", "schema": "Vehicle"}' | websocat ws://localhost:8080 -n | jq
 ```
 
 On success:
+
 ```yaml
 {
   "type": "status",
   "code": 200,
   "message": "Successfully subscribed",
-  "timestamp": {
-    "seconds": 1738613971,
-    "nanos": 955000000
-  }
+  "timestamp": { "seconds": 1738613971, "nanos": 955000000 },
 }
 ```
+
 ## Unsubscribe
 
 ```yaml
-{
-  "type": "unsubscribe",
-  "schema": "Vehicle",
-  "instance": "VIN_123"
-}
+{ "type": "unsubscribe", "schema": "Vehicle", "instance": "VIN_123" }
 ```
 
 On success:
+
 ```yaml
 {
   "type": "status",
   "code": 200,
   "message": "Successfully unsubscribed",
-  "timestamp": {
-    "seconds": 1738614001,
-    "nanos": 562000000
-  }
+  "timestamp": { "seconds": 1738614001, "nanos": 562000000 },
 }
 ```
-