EV car and server project

An EV company is about to begin delivery of a massive number vehicles. They need to communicate with all vehicles by their VIN numbers (string) in real-time to: · Collect location, assume (x,y) coordinates as integers only for this exercise, on a regular basis (5 seconds intervals) · Collect current speed (integer) · Inquire about the drive status ("parked", "driving", "reverse", a string) You are tasked with building a server application as well as an application that runs on each vehicle. The company vehicle administrator will require command interface (CLI, REPL, or Web App) to display a list of vehicles and all related information. The vehicles will communicate with the server over a reliable communication protocol where messages between the server and vehicle are not lost when either the vehicle or the server is shutdown and are delivered in order. Do not use an off-the-shelf package like MQTT, RabbitMQ, or Kafka. Design a protocol over TCP, WebSockets, or GRPC for example. For this project assume the total number of cars on the road are 3 only. So run 1 server, and 3 vehicles. Bonus I: One, and only one, vehicle is designated as "pace" vehicle. If the pace vehicle is disconnected, another vehicle is designated as the official pace vehicle within 5 seconds. Bonus II: Describe your plans for an architecture, server and vehicle software, to manage scaling to 3M additional cars every year. Incorporating Open Source projects or protocols is ok here.