What is this

This project is intended to provide a playground for testing various components of a web application.

The requirement for the application is to process updates to reviews, decorate them with metadata and render this to the user.

This allows me to implement a simple version of a series of components and from there either a) test a new technolgy as part of a system b) learn about a new system.

Some of the derired traits of the system are;

• Minimum number of dependencies between services
• Abstract the underlying technologies behind APIs used so new ones can be tested
• No tests are required, this is a playground
• The APIs are all RESTful with JSON as the interchange format

Components

Bond Movie API

Command Application that monitors local markdown files for changes. The primary focus of this to test web frameworks and database implementations.

• Node.js (Port: 3001) + DynamoDB (Shared) (Port: 8000)
• Java (Port: 3002) + Spring Boot + Hibernate + DynamoDB (Shared) (Port: 8000)
• Java (Port: 3003) + Spring Boot + Hibernate + PostgreSQL (Port: 5432)

Metadata API

Metadata API which caches metadata taken from an external API. The primary focus of this service is to test cache infrastructure and caching libraries. There are two supported metadata stores; a) The Movie Database b) The Open Movie Database.

• Node.js (Port: 3004) + node redis + Redis (Port: 6375)
• Java (Port: 3008) + Spring Boot + Redis (Port: 6375)

Process Queue API

Queue API which processes updated Bond movie reviews.

• Node.js (Port: 3006) + kafkajs + Kafka (Shared) (Port: 9092)
• Node.js (Port: 3009) + Redis (Port: 6375)
• Java (Port: 3010) + Spring Boot + Camel + Kafka (Shared) (Port: 9092)

Watch Reviews

RESTful API for accessing Bond movie reviews with their metadata

• Node.js + glob-watcher + showdown

UI

UI for the end user to consume the RESTful API

• Node.js (Port: 3007) + Vanilla js

Running the System

Quick Start

docker compose up

This starts services based on COMPOSE_PROFILES in .env. Infrastructure (DynamoDB, Redis, Kafka, etc.) starts automatically via depends_on.

Switching Implementations

Edit COMPOSE_PROFILES in .env to choose which implementations to run:

# .env
COMPOSE_PROFILES=bond-nodejs,metadata-nodejs,queue-kafkajs,ui,watch

Available Profiles

API	Profile	Description
Bond Movies	bond-nodejs	Node.js + DynamoDB (port 3001)
	bond-spring-dynamodb	Spring + DynamoDB (port 3002)
	bond-spring-postgresql	Spring + PostgreSQL (port 3003)
Metadata	metadata-nodejs	Node.js + Redis (port 3004)
	metadata-spring	Spring + Redis (port 3008)
Process Queue	queue-kafkajs	Node.js + kafkajs (port 3006)
	queue-redis	Node.js + Redis (port 3009)
	queue-spring-camel	Spring + Camel + Kafka (port 3010)
UI	ui	Vanilla JS (port 3007)
Watch	watch	File watcher service
Tools	pgadmin	PostgreSQL admin UI (port 5050)

Example: Switch to Java Stack

# .env
COMPOSE_PROFILES=bond-spring-dynamodb,metadata-spring,queue-spring-camel,ui,watch

BOND_MOVIES_API_URL=http://bond-movies-api-spring-dynamodb:3002
MOVIE_METADATA_API_URL=http://movie-metadata-api-spring:3008
REVIEW_UPDATES_API_URL=http://review-updates-api-spring-camel-kafka:3010

Note: Spring services require Maven builds first:

cd bond-movies-api-spring-dynamodb && ./mvnw package -DskipTests && cd ..

E2E Testing

End-to-end API tests using Bruno ensure all implementations conform to the same API contract.

Setup

cd e2e-tests
npm install

Run Tests

# Test Bond Movies API against Node.js implementation
npm run test:bond-movies:nodejs

# Test against Spring + DynamoDB implementation
npm run test:bond-movies:spring-dynamodb

# Test against Spring + PostgreSQL implementation
npm run test:bond-movies:spring-postgresql

Using Bruno GUI

1. Download Bruno from https://www.usebruno.com/
2. Open Collection → select e2e-tests/bond-movies-api
3. Select environment from dropdown
4. Run tests

Tests are reusable across implementations - the same test suite validates that Node.js and Spring implementations behave identically.

Environment Variables

In the .env file there is the current configuration for the interconnection of the services. Changing the URLs here to point at other services will reconfigure dependent services. For example, change REVIEW_UPDATES_API_URL to test another queue implementation.

Name	Default	Description
BOND_ENV	local	The current operating environment. local (default) and docker are supported.
BOND_MOVIES_API_URL	http://bond-movies-api-nodejs:3001	The internal docker URL for the bond movies api service
MOVIE_METADATA_API_URL	http://movie-metadata-api-nodejs:3004	The internal docker URL for the metadata service
REVIEW_UPDATES_API_URL	http://review-updates-api-nodejs-kafkajs-kafka:3006	The internal docker URL for the review updates service

Kafka

It is sometimes desirable to interact with Kafka directly. The following commands can be used to perform some standard tasks;

List Topics

docker exec -it $(docker ps -aqf "name=kafka1") kafka-topics --list --bootstrap-server localhost:9092

Create the Bond Movie topic

docker exec -it $(docker ps -aqf "name=kafka1") kafka-topics --create --topic BondMoviesToBeProcessed --bootstrap-server localhost:9092

Describe Bond Movie topic

docker exec -it $(docker ps -aqf "name=kafka1") kafka-topics --describe --topic BondMoviesToBeProcessed --bootstrap-server localhost:9092

List all queued items and listen for new items

docker exec -it $(docker ps -aqf "name=kafka1") kafka-console-consumer --topic BondMoviesToBeProcessed --from-beginning --bootstrap-server localhost:9092

Interactive prompt to directly inject new items

docker exec -it $(docker ps -aqf "name=kafka1") kafka-console-producer --topic BondMoviesToBeProcessed --broker-list localhost:9092