rpitty/video-series-app
43.0
Weak · 22 September 2026
278
lines of production code
Java
primary language
6
measurements over time
What this system is
This system is a video series management application built on a CQRS architecture using the Axon Framework. It separates command and query responsibilities into distinct services, utilizing event sourcing with MongoDB for state persistence and an H2 database for query-side data. The application exposes REST APIs to create and retrieve video series information.
Features
Add video-series-query service with CQRS query handling
The video-series-query module is introduced, providing a Spring Boot application that exposes a REST endpoint at /video-series to retrieve all video series. The service uses Axon Framework to handle the FindAllVideoSeriesQuery, which is processed by VideoSeriesEventHandler to fetch data from a JPA repository backed by an H2 database. The module includes the necessary Java classes (launcher, entity, repository, query, handler, and controller), along with configuration files (application.properties, schema.sql, data.sql) and a LICENSE file.
video-series-query · high confidence
Added Axon framework configuration and domain models for video series
The video-series-core module now includes the Apache 2.0 license and a README. Functionally, it introduces the core domain model (VideoSeriesDto, AddSeriesEvent) and the Axon framework configuration (AxonConfig) which sets up MongoDB-based token and event storage engines for the application's event sourcing architecture.
video-series-core · high confidence
Introduce video-series command service with CQRS architecture
Adds the video-series command service, a Spring Boot application implementing a CQRS (Command Query Responsibility Segregation) architecture using Axon Framework. The service exposes a REST API at /video-series to accept video series data (name, volumes, genre, cash value) and processes commands via an aggregate, persisting state in an H2 database and MongoDB. Includes the application launcher, REST controller, command and event handling logic, and configuration files.
video-series-command · high confidence
Dependencies
Initial Maven build configuration for the video-series-app
The project now includes a root pom.xml and module-specific pom.xml files for video-series-command, video-series-core, and video-series-query. These files establish a multi-module Maven build, defining dependencies such as Spring Boot 2.2.2, Axon 4.2, H2, Lombok, and various test libraries (JUnit 5, Mockito, AssertJ, Flapdoodle embedded MongoDB).
(dependencies) · high confidence
Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 48 → 43 (-5.2)
- Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.
Lenses
- Code Health 100 → 100 (+0.0)
- Architecture 100 → 81 (-18.9)
- Maturity 45 → 45 (+0.0)
- Readiness 17 → 17 (+0.0)
- Security 100 → 100 (+0.0)
- Domain Modelling 100 → 73 (-27.4)
- Event Sourcing 100 → 100 (+0.0)
Resolved (8)
- Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- LLM evaluation failed
- No exposed public API
- Scanner failed to run — not a clean result
- early-stage repository — too little history to judge knowledge freshness
- git history depth insufficient
- git history depth insufficient
- single-maintainer — knowledge-concentration (bus factor) risk
New (5)
- Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
- Documentation: no installation or build instructions (README.md)
- No ADRs found
- Scanner failed to run — not a clean result
- Scanner failed to run — not a clean result
Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
rpitty/video-series-app was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 22 September 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 9fb912349c1aac0cbb07254844abff1b50b709f0 — the exact code this score is about.
- Scored under rubric-2026.09.15 — the same rubric and the same method as every other entry in this index.
- Measured by watchdog.canine.dev using codehealth-analyzer preprod-821afab8930d.