Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/rgolubtsov/transroutownish-proto-bus-spring-boot
A Spring Boot-based application, designed and intended to be run as a microservice, implementing a simple urban bus routing prototype.
https://github.com/rgolubtsov/transroutownish-proto-bus-spring-boot
java json microservice rest routing spring-boot transportation
Last synced: 7 days ago
JSON representation
A Spring Boot-based application, designed and intended to be run as a microservice, implementing a simple urban bus routing prototype.
- Host: GitHub
- URL: https://github.com/rgolubtsov/transroutownish-proto-bus-spring-boot
- Owner: rgolubtsov
- License: mit
- Created: 2021-09-21T13:40:20.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2024-06-20T12:30:25.000Z (6 months ago)
- Last Synced: 2024-10-31T09:21:03.542Z (about 2 months ago)
- Topics: java, json, microservice, rest, routing, spring-boot, transportation
- Language: Java
- Homepage:
- Size: 281 KB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Trans-RoutE-Townish (transroutownish) :small_blue_diamond: Urban bus routing microservice prototype
**A Spring Boot-based application, designed and intended to be run as a microservice,
implementing a simple urban bus routing prototype**
Consider an IoT system that aimed at planning and forming a specific bus route for a hypothetical passenger. One crucial part of such system is a **module**, that is responsible for filtering bus routes between two arbitrary bus stops where a direct route is actually present and can be easily found. Imagine there is a fictional urban public transportation agency that provides a wide series of bus routes, which covered large city areas, such that they are consisting of many bus stop points in each route. Let's name this agency **Trans-RoutE-Townish Co., Ltd.** or in the Net representation — **transroutownish.com**, hence the name of the project.
A **module** that is developed here is dedicated to find out quickly, whether there is a direct route in a list of given bus routes between two specified bus stops. It should immediately report back to the IoT system with the result `true` if such a route is found, i.e. it exists in the bus routes list, or `false` otherwise, by outputting a simple JSON structure using the following format:
```
{
"from" : ,
"to" : ,
"direct" : true
}
```
`` and `` above are bus stop IDs: unique positive integers, taken right from inputs.
A bus routes list is a plain text file where each route has its own unique ID (positive integer) and a sequence of its bus stop IDs. Each route occupies only one line in this file, so that they are all representing something similar to a list — the list of routes. The first number in a route is always its own ID. Other consequent numbers after it are simply IDs of bus stops in this route, up to the end of line. All IDs in each route are separated by whitespace, usually by single spaces or tabs, but not newline.
There are some constraints:
1. Routes are considered not to be a round trip journey, that is they are operated in the forward direction only.
2. All IDs (of routes and bus stops) must be represented by positive integer values, in the range `1 .. 2,147,483,647`.
3. Any bus stop ID may occure in the current route only once, but it might be presented in any other route too.
The list of routes is usually mentioned throughout the source code as a **routes data store**, and a sample routes data store can be found in the `data/` directory of this repo.
Since the microservice architecture for building independent backend modules of a composite system are very prevalent nowadays, this seems to be natural for creating a microservice, which is containerized and run as a daemon, serving a continuous flow of HTTP requests.
This microservice is intended to be built locally and to be run like a conventional daemon in the VM environment, as well as a containerized service, managed by Docker.
One may consider this project has to be suitable for a wide variety of applied areas and may use this prototype as: (1) a template for building a similar microservice, (2) for evolving it to make something more universal, or (3) to simply explore it and take out some snippets and techniques from it for *educational purposes*, etc.
---
## Table of Contents
* **[Building](#building)**
* **[Creating a Docker image](#creating-a-docker-image)**
* **[Running](#running)**
* **[Running a Docker image](#running-a-docker-image)**
* **[Exploring a Docker image payload](#exploring-a-docker-image-payload)**
* **[Consuming](#consuming)**
* **[Logging](#logging)**
* **[Error handling](#error-handling)**
## Building
The microservice might be built and run successfully under **Ubuntu Server (Ubuntu 22.04.3 LTS x86-64)**. Install the necessary dependencies (`openjdk-17-jdk-headless`, `make`, `docker.io`):
```
$ sudo apt-get update && \
sudo apt-get install openjdk-17-jdk-headless make docker.io -y
```
**Build** the microservice using **Maven Wrapper**:
```
$ ./mvnw clean
...
$ ./mvnw compile
...
$ ./mvnw package
...
```
Or **build** the microservice using **GNU Make** (optional, but for convenience — it covers the same **Maven Wrapper** build workflow under the hood):
```
$ make clean
...
$ make # <== Compilation phase.
...
$ make jar
...
$ make all # <== Or make all the targets at one pass: compile, jar.
...
```
### Creating a Docker image
**Build** a Docker image for the microservice:
```
$ # Pull the JRE image first, if not already there:
$ sudo docker pull azul/zulu-openjdk-alpine:17-jre-headless-latest
...
$ # Then build the microservice image:
$ sudo docker build -ttransroutownish/bus .
...
```
## Running
**Run** the microservice using **Maven Wrapper** (generally for development and debugging purposes):
```
$ ./mvnw spring-boot:run; echo $?
$ # ^ ^ ^
$ # | | |
$ # --------------------+---+---+
$ # Whilst this is not necessary, it's beneficial knowing the exit code.
...
```
**Run** the microservice using its all-in-one JAR file, built previously by the `package` or `jar` targets:
```
$ java -jar target/bus-0.30.5.jar; echo $?
...
```
### Running a Docker image
**Run** a Docker image of the microservice:
```
$ export PORT=8765 && sudo docker run -dp${PORT}:${PORT} --name bus transroutownish/bus; echo $?
...
```
If Docker will complain that the container name is already in use (after subsequent creation of a new container), like the following:
```
docker: Error response from daemon: Conflict.
The container name "/bus" is already in use by container "".
You have to remove (or rename) that container to be able to reuse that name.
...
```
...it's safe to remove that container: `$ sudo docker rm bus`, and run the image once again.
Yet even better, a Docker image might be run by issuing a compound command, beginning with deleting all stopped containers:
```
$ sudo docker rm `sudo docker ps -aq`; \
export PORT=8765 && sudo docker run -dp${PORT}:${PORT} --name bus transroutownish/bus; echo $?
...
```
### Exploring a Docker image payload
The following is not necessary but might be considered interesting — to look up into the running container, and check out that the microservice's JAR layers, log, and routes data store are at their expected places and in effect:
```
$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
transroutownish/bus "java org.springfram..." About an hour ago Up About an hour 0.0.0.0:8765->8765/tcp, :::8765->8765/tcp bus
$
$ sudo docker exec -it bus sh; echo $?
/var/tmp $
/var/tmp $ java --version
openjdk 17.0.9 2023-10-17 LTS
OpenJDK Runtime Environment Zulu17.46+19-CA (build 17.0.9+8-LTS)
OpenJDK 64-Bit Server VM Zulu17.46+19-CA (build 17.0.9+8-LTS, mixed mode, sharing)
/var/tmp $
/var/tmp $ ls -al
total 32
drwxrwxrwt 1 root root 4096 Nov 17 10:40 .
drwxr-xr-x 1 root root 4096 Sep 28 11:18 ..
drwxr-xr-x 1 nobody nobody 4096 Nov 17 10:00 BOOT-INF
drwxr-xr-x 3 nobody nobody 4096 Nov 17 10:00 META-INF
drwxr-xr-x 2 root root 4096 Nov 17 10:00 data
drwxr-xr-x 2 daemon daemon 4096 Nov 17 10:40 log
drwxr-xr-x 3 nobody nobody 4096 Nov 17 10:00 org
/var/tmp $
/var/tmp $ ls -al BOOT-INF/ data/ log/
BOOT-INF/:
total 24
drwxr-xr-x 1 nobody nobody 4096 Nov 17 10:00 .
drwxrwxrwt 1 root root 4096 Nov 17 10:40 ..
drwxr-xr-x 3 nobody nobody 4096 Nov 17 10:00 classes
-rw-r--r-- 1 nobody nobody 1978 Nov 17 2023 classpath.idx
-rw-r--r-- 1 nobody nobody 212 Nov 17 2023 layers.idx
drwxr-xr-x 2 nobody nobody 4096 Nov 17 10:00 lib
data/:
total 56
drwxr-xr-x 2 root root 4096 Nov 17 10:00 .
drwxrwxrwt 1 root root 4096 Nov 17 10:40 ..
-rw-r--r-- 1 root root 46218 Nov 17 06:35 routes.txt
log/:
total 12
drwxr-xr-x 2 daemon daemon 4096 Nov 17 10:40 .
drwxrwxrwt 1 root root 4096 Nov 17 10:40 ..
-rw-r--r-- 1 daemon daemon 468 Nov 17 10:40 bus.log
/var/tmp $
/var/tmp $ netstat -plunt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8765 0.0.0.0:* LISTEN 1/java
/var/tmp $
/var/tmp $ ps ax
PID USER TIME COMMAND
1 daemon 0:06 java org.springframework.boot.loader.JarLauncher
67 daemon 0:00 sh
94 daemon 0:00 ps ax
/var/tmp $
/var/tmp $ exit # Or simply .
0
```
## Consuming
All the routes are contained in a so-called **routes data store**. It is located in the `data/` directory. The default filename for it is `routes.txt`, but it can be specified explicitly (if intended to use another one) in the `src/main/resources/application.properties` file.
**Identify**, whether there is a direct route between two bus stops with IDs given in the **HTTP GET** request, searching for them against the underlying **routes data store**:
HTTP request param | Sample value | Another sample value | Yet another sample value
------------------ | ------------ | -------------------- | ------------------------
`from` | `4838` | `82` | `2147483647`
`to` | `524987` | `35390` | `1`
The direct route is found:
```
$ curl 'http://localhost:8765/route/direct?from=4838&to=524987'
{"from":4838,"to":524987,"direct":true}
```
The direct route is not found:
```
$ curl 'http://localhost:8765/route/direct?from=82&to=35390'
{"from":82,"to":35390,"direct":false}
```
### Logging
The microservice has the ability to log messages to a logfile and to the Unix syslog facility. When running under Ubuntu Server (not in a Docker container), logs can be seen and analyzed in an ordinary fashion, by `tail`ing the `log/bus.log` logfile:
```
$ tail -f log/bus.log
...
[2023-11-17][13:05:29][INFO ] Server started on port 8765
[2023-11-17][13:15:08][DEBUG] from=4838 | to=524987
[2023-11-17][13:15:08][DEBUG] 1 = 1 2 3 4 5 6 7 8 9 987 11 12 13 4987 415 ...
...
[2023-11-17][13:15:30][DEBUG] from=82 | to=35390
[2023-11-17][13:15:30][DEBUG] 1 = 1 2 3 4 5 6 7 8 9 987 11 12 13 4987 415 ...
...
[2023-11-17][13:20:44][INFO ] Server stopped
```
Messages registered by the Unix system logger can be seen and analyzed using the `journalctl` utility:
```
$ journalctl -f
...
Nov 17 13:05:29 java[]: Server started on port 8765
Nov 17 13:15:08 java[]: from=4838 | to=524987
Nov 17 13:15:30 java[]: from=82 | to=35390
Nov 17 13:20:44 java[]: Server stopped
```
Inside the running container logs might be queried also by `tail`ing the `log/bus.log` logfile:
```
/var/tmp $ tail -f log/bus.log
...
[2023-11-17][10:40:11][INFO ] Server started on port 8765
[2023-11-17][10:50:10][DEBUG] from=4838 | to=524987
[2023-11-17][10:50:10][DEBUG] 1 = 1 2 3 4 5 6 7 8 9 987 11 12 13 4987 415 ...
...
[2023-11-17][10:50:25][DEBUG] from=82 | to=35390
[2023-11-17][10:50:25][DEBUG] 1 = 1 2 3 4 5 6 7 8 9 987 11 12 13 4987 415 ...
...
```
And of course Docker itself gives the possibility to read log messages by using the corresponding command for that:
```
$ sudo docker logs -f bus
...
[2023-11-17][10:40:11][INFO ] Server started on port 8765
...
[2023-11-17][10:50:10][DEBUG] from=4838 | to=524987
[2023-11-17][10:50:10][DEBUG] 1 = 1 2 3 4 5 6 7 8 9 987 11 12 13 4987 415 ...
...
[2023-11-17][10:50:25][DEBUG] from=82 | to=35390
[2023-11-17][10:50:25][DEBUG] 1 = 1 2 3 4 5 6 7 8 9 987 11 12 13 4987 415 ...
...
[2023-11-17][10:55:15][INFO ] Server stopped
```
### Error handling
When the query string passed in a request, contains inappropriate input, or the URI endpoint doesn't contain anything else at all after its path, the microservice will respond with the **HTTP 400 Bad Request** status code, including a specific response body in JSON representation, like the following:
```
$ curl 'http://localhost:8765/route/direct?from=qwerty4838&to=-i-.;--089asdf../nj524987'
{"error":"Request parameters must take positive integer values, in the range 1 .. 2,147,483,647. Please check your inputs."}
```
Or even simpler:
```
$ curl http://localhost:8765/route/direct
{"error":"Request parameters must take positive integer values, in the range 1 .. 2,147,483,647. Please check your inputs."}
```