3rd ICAI 2024

International Conference on Automotive Industry 2024

Mladá Boleslav, Czech Republic

Figure 1: System Architecture

Source: Mouna Amrou M’hand et al 2019 As shown on the figure 1, Microservice1MessageBroker facilitates communication with portals, gathering real-time scanned data such as driver, vehicle, and provider information. This microservice manages event streams by publishing and subscribing to them, utilizing Kafka for fault-tolerance and scalability. Microservice2DataCollection interfaces with Microservice1MessageBroker to store data in MongoDB, a NoSQL document database chosen for its flexibility, search capabilities, and sharding technique suitable for large datasets. Microservice3Mining retrieves event data from Microservice2 to conduct process mining, leveraging PROM6, a process mining toolset, to unveil operational process insights, identify bottlenecks, and prioritize issues and root causes. Lastly, Microservice4Alert works in conjunction with preceding microservices to alert anomalies like unusual behavior, bottlenecks, or traffic flow decreases. 5.4.1 Technical Implementation: APIs, Containers, and Orchestration APIs (Application Programming Interfaces): Serve as the communication link between microservices, enabling data exchange and function calls. Containers: Provide a lightweight, portable environment for deploying microservices, ensuring consistency across development, testing, and production environments. Orchestration Tools: Tools like Kubernetes manage the deployment, scaling, and operation of containerized(Vincek et al., 2017)

134