Angular2Guy/MovieManager

MovieManager is a full-stack web application for managing movie and actor data, featuring an Angular frontend and a Spring Boot backend. It provides capabilities for user authentication, searching and filtering content, and importing movie details from TheMovieDB API. The system is deployed via Docker and Kubernetes, utilizing PostgreSQL for storage and Kafka for event-driven communication.

16 changes.

The project was initialized with a modernized technology stack, upgrading to Spring Boot 4.1, Angular 22, and Java 25, while establishing an AOT-optimized Docker build environment. This period involved stripping out all legacy Angular and Spring Boot code, including old components, services, and security configurations, to prepare the codebase for a fresh implementation.

26 changes.

This period focused on building the MovieManager application from scratch, establishing a Java backend with Kafka integration and an Angular frontend using standalone components and signals. The work included implementing core domain features for movies and actors, setting up comprehensive Kubernetes deployment via Helm charts, and initializing the project with essential DevOps and architecture documentation.

Introduces a new Helm chart (kafkadev) that deploys a Kafka broker and a Zookeeper instance for local development. The chart provisions Kubernetes Secrets for application and database configuration, Persistent Volumes and Claims for storage, and Deployments for both the Kafka application (using the bitnami/kafka image) and the Zookeeper service (using the bitnami/zookeeper image). It also configures Services to expose the Kafka broker on port 9092 via a NodePort and the Zookeeper service on port 2181, with environment variables wired from the defined secrets and normal values.

helm/kafka · high confidence

Users can now import movies by title. The new MovieImportComponent listens for a movie name in the URL query parameters, fetches matching results via the MoviesService, and displays them in a table. Users can click a movie to initiate the import, which shows a loading spinner during the process and provides success or failure feedback before redirecting back to the search page.

frontend/src/angular/src/app/movie-import · high confidence

The frontend module now includes standard Eclipse IDE metadata files (.classpath, .project, and .gitignore). These files configure the project for the Eclipse IDE, defining source and test directories, setting up the Java 25 runtime environment, and enabling Maven integration, which facilitates local development and project import for users working within that specific IDE.

frontend · high confidence

Added two new shell scripts to the Helm directory: \helm.sh\ provides commented-out commands for installing and deleting Helm charts (Kafka, moviemanager, moviemanagerwithkafka), and \minikubeSetup.sh\ provides a sequence of commands for configuring and starting a Minikube cluster with specific resource limits and enabled addons.

helm · high confidence

The Angular frontend application has been initialized with a new project structure, including environment configurations for production and development modes, a standalone application bootstrap entry point, and global styles importing Bootstrap. The project also includes standard polyfills for browser compatibility, testing setup, and the main HTML entry point, establishing the foundational runtime and styling for the application.

frontend/src/angular/src · high confidence

The Angular application in this location has been initialized with a new configuration structure. It now supports internationalization (i18n) with German locale files and uses the modern \@angular-devkit/build-angular\ builder for building and serving. Code quality is enforced via a new ESLint configuration extending Angular-specific plugins, and the test environment (Karma) has been updated to support headless Chrome and Chromium execution for CI/CD compatibility.

frontend/src/angular · high confidence

This change introduces the core backend adapter components for the MovieManager application. It includes REST controllers for managing movies, actors, and user authentication, along with a new RestClient implementation for fetching data from TheMovieDB API. Configuration classes establish security (JWT filtering, XSS protection), Kafka integration for event-driven user sessions, and scheduled jobs for data migration and cleanup. Additionally, a servlet filter is added to handle frontend routing and locale detection, and a global exception handler standardizes error responses.

backend/src/main/java · high confidence

The application now uses Liquibase for database schema management, replacing the previous static SQL initialization script. This change introduces a comprehensive set of migration files (db.changelog-1.0.xml through 8.0.xml) that define the core domain model, including tables for movies, actors, users, and their relationships, along with necessary indexes and constraints. It also adds support for distributed locking via the ShedLock table, implements an event publication table to support the transactional outbox pattern, and refines user account fields with unique constraints and new columns for security status. Additionally, initial seed data for movies, actors, and users is now loaded automatically via Liquibase changelogs.

backend/src/main/resources/db · high confidence

This change introduces the initial Helm chart templates for deploying the Movie Manager application stack. It adds a helper template (\_helpers.tpl) to manage environment variable injection from Kubernetes Secrets for the application, database, and Kafka components. The kubTemplate.yaml file defines the core Kubernetes resources, including Secrets for configuration, PersistentVolumes and Claims for PostgreSQL data storage, and Deployments and Services for the database (PostgreSQL), Kafka broker, and the web application, establishing the foundational infrastructure for the stack.

helm/moviemanagerwithkafka/templates · high confidence

Adds a new Helm chart (moviemanager v0.1.0) that deploys the MovieManager application stack to Kubernetes. The chart provisions a PostgreSQL database (v13) with persistent storage and a web application container (based on angular2guy/moviemanager:latest) with health probes. It configures environment variables for both components, including database credentials and JWT secrets, and exposes the web service via a NodePort on port 8080.

helm/moviemanager · high confidence

This change introduces the initial Helm chart structure for the MovieManager application, enabling deployment on Kubernetes with Kafka support. The chart defines configuration values for the web application (using the \angular2guy/moviemanager\ image), a PostgreSQL database (version 13), and Kafka/Zookeeper components (via Bitnami images). It includes specific environment variable configurations for Kafka (node ID, listeners, controller quorum), database credentials, and application settings (including JWT secrets and Tink encryption keys), along with a \.helmignore\ file to exclude local development artifacts during packaging.

helm/moviemanagerwithkafka · high confidence

Added a new \structurizr\ directory containing the initial Component diagram for the MovieManager system. This documentation visualizes the application's architecture, including the Angular Frontend, Kafka Producer/Consumer components, various REST controllers (Auth, Movie/Actor, Import), Services, and Repositories, along with their interactions via REST requests and Kafka events.

structurizr · high confidence

The backend now includes dedicated configuration profiles for local and production Kafka integration, enabling transactional messaging with idempotent producers and read-committed consumer isolation. A production-specific profile is added to configure PostgreSQL connectivity and JPA validation, while the main application properties establish baseline settings for JWT security, H2 in-memory database usage, Hibernate Search indexing, and comprehensive Spring Boot Actuator metrics (Prometheus) and health checks.

backend/src/main/resources · high confidence

The repository is initialized with the core configuration files for the MovieManager application, including the Eclipse project descriptor, Travis CI build script, and Dockerfile. The Dockerfile is configured to use the Eclipse Temurin JDK 25 base image and incorporates an Ahead-Of-Time (AOT) cache (app.aot) to optimize startup performance, alongside specific JVM memory and garbage collection settings. Supporting scripts are added to facilitate local development environments for PostgreSQL, Kafka (KRaft), Prometheus, and Grafana, while the README documents the technology stack (Angular, Spring Boot, Hibernate Search) and setup instructions.

(repo-wide) · high confidence

This change introduces the foundational data models required for the application's movie and actor management features. New TypeScript classes and interfaces have been added to \frontend/src/angular/src/app/model\, including \Actor\, \Movie\, \Cast\, and \Genere\ to represent core entities, alongside \ActorFilterCriteria\ and \MovieFilterCriteria\ to support filtering logic. Additionally, search capabilities are enabled through the introduction of \SearchTerm\, \SearchString\, and \SearchPhrase\ models, while \User\ and \common\ utilities (such as \QueryParam\ and \FulltextFilter\) provide necessary support structures for authentication and navigation.

frontend/src/angular/src/app/model · high confidence

Added new Angular services (ActorsService, MoviesService, UsersService) that provide HTTP-based access to the backend REST API. ActorsService enables retrieving actors by ID, name, or filter criteria. MoviesService supports paginated listing, retrieval by ID, title, or genre, filtering, deletion, and importing movies by title or MovieDb ID, along with fetching available genres. UsersService handles user login and sign-in, integrating with a TokenService to manage authentication tokens and user IDs upon successful login.

frontend/src/angular/src/app/services · high confidence

The login interface has been implemented as a new standalone Angular component (\app-login\) that presents a modal dialog for user authentication. Users can now enter their login name, password, and an optional MovieDb key to either log in or create a new account (signin). The form includes client-side validation, displays error or info messages via alerts, and shows a loading spinner while waiting for server responses. The component uses Angular signals for state management and integrates with \UsersService\ for backend communication and \TokenService\ for session handling.

frontend/src/angular/src/app/login · high confidence

A new standalone Angular component has been added to allow users to filter actors by name, gender, birth date range, popularity, and movie character roles. The interface supports full-text search within biographies, offering both phrase and word-based filtering modes, and presents these options in an offcanvas panel for easy access.

frontend/src/angular/src/app/filter-actors · high confidence

Users can now access a dedicated movie filtering interface via an offcanvas panel. This new component allows filtering by release date range, title, actor, genre, minimum/maximum length, and minimum rating. It supports full-text search with options to switch between phrase and word filters, and includes a reset function to clear active filters. The interface is built using Angular signals and standalone components, integrating with the existing movie service to fetch and display filtered results.

frontend/src/angular/src/app/filter-movies · high confidence

The search page now provides a unified interface for discovering content: users can search for movies by title or actors by name, with results appearing in dropdowns as they type. A genre filter allows browsing movies by category, and a scrollable table displays movie details (title, release date, genres, overview) with double-click navigation to individual movie pages. The component also includes a login overlay and an import movie feature that navigates to a dedicated import flow.

frontend/src/angular/src/app/search · high confidence

The application now includes a new standalone component for viewing individual actor details. This page displays the actor's name, birthday (formatted as dd.MM.yyyy), biography, gender, and place of birth. It also lists the actor's cast roles, linking each movie title to its respective detail page. Navigation back to the search or filter-actors view is handled via query parameters. The component uses Angular signals for state management and OnPush change detection.

frontend/src/angular/src/app/actors · high confidence

The movies area now uses a new standalone Angular component that displays movie details (title, release date, overview, genres, and cast) and allows users to delete a movie. The component leverages Angular signals for state, OnPush change detection, and the new control flow syntax (@if, @for) in the template. It includes a 'Back' button that dynamically routes to either /search or /filter-movies based on query parameters, and handles movie deletion via the MoviesService, navigating back to /search upon success. The component is located in frontend/src/angular/src/app/movies.

frontend/src/angular/src/app/movies · high confidence

The dedicated components for viewing individual actor and movie details (including their HTML templates, TypeScript logic, and unit tests) have been removed from the application. This eliminates the previous UI for displaying specific actor profiles (name, birthday, biography, gender, place of birth, and cast history) and movie details (title, release date, overview, genres, and cast), along with the ability to delete movies from the movie detail page.

src/angular/moviemanager/src/app/actors · high confidence

The core Angular application structure located in \src/angular/moviemanager/src/app\ has been removed. This includes the deletion of the main application module (\app.module.ts\), the root component (\app.component.ts\ and its template), the routing configuration (\app-routing.module.ts\), and the associated environment files (\environment.ts\ and \environment.prod.ts\). Consequently, the application no longer bootstraps the \AppComponent\, defines routes for search, movie, or actor views, or manages services like \MoviesService\ and \ActorsService\ within this specific module context.

src/angular/moviemanager/src/app · high confidence

The legacy HTTP-based services for managing actors, movies, and users, along with their corresponding unit tests, have been removed from the application. This cleanup eliminates the old implementation that relied on direct HttpClient calls and manual RxJS operator imports, indicating a shift toward a different architectural approach for data access and user management.

src/angular/moviemanager/src/app/services · high confidence

The legacy JPA entity classes for Genere, Movie, and User have been removed from the application model. This change eliminates the previous data structure definitions that included specific mappings for movie genres, cast relationships, and user roles, indicating a shift away from this specific entity schema in the current version.

src/main/java/ch/xxx/moviemanager/model · high confidence

The legacy REST controllers for actors, movies, user login/sign-in, and movie imports have been removed from the application. This eliminates the previous endpoints for searching actors and movies by name or ID, managing user authentication, retrieving genres, and importing movies, indicating a shift away from these specific API interfaces.

src/main/java/ch/xxx/moviemanager/rest · high confidence

The shared model definitions for Actor, Cast, Genere, Movie, and User have been removed from the application's common module. This cleanup eliminates the local TypeScript interfaces that previously defined the structure for these entities, indicating a shift in how data models are managed or imported within the MovieManager application.

src/angular/moviemanager/src/app/common · high confidence

The legacy search component, which provided functionality to search for movies by title or actor, browse genres, and import movies by title, has been removed from the application. This deletion includes the associated HTML template, SCSS styles, TypeScript logic, and unit tests, indicating that this search interface is no longer part of the product.

src/angular/moviemanager/src/app/login, src/angular/moviemanager/src/app/search · high confidence

The \AppUserDetailsService\ and \MovieManagerService\ classes have been removed from the application. This eliminates the previous manual implementation of user authentication logic and the core movie management business logic, which previously handled user registration, movie CRUD operations, and external API integrations directly within these service components.

src/main/java/ch/xxx/moviemanager/service · high confidence

The backend project now targets the Java 25 runtime environment, as indicated by the Eclipse classpath configuration. Additionally, a static landing page (index.html) has been added to the resources directory, which automatically redirects users to localized versions of the site (German or English) based on their browser language settings.

backend · medium confidence

Users are now presented with a language selection page (index.html) that automatically redirects to either the German or English version of the application based on their browser language, with manual links provided as a fallback. Additionally, the end-to-end testing infrastructure has been reorganized: test files and configuration have been moved from the moviemanager module to a centralized e2e directory, and the TypeScript output directory for these tests has been updated to align with the main application build output.

frontend/src/angular/base, frontend/src/angular/e2e · high confidence

A new SVG spinner asset has been added to the frontend assets, providing a visual loading indicator for the application. Additionally, an unused styles file from the movie manager component has been removed and replaced with a placeholder to maintain the directory structure.

frontend/src/angular/src/assets · high confidence

The application shell has been refactored to use Angular's standalone components and the new signal-based API. The root component now uses the \imports\ array to declare dependencies like \RouterModule\ directly, and the application configuration (\app.config.ts\) utilizes the modern \ApplicationConfig\ provider model. Additionally, the component's internal state for the title has been converted to a signal, and the logout flow now navigates to a specific route before clearing the token, reflecting a shift toward the new standalone architecture.

frontend/src/angular/src/app · high confidence

The project has removed several legacy configuration files, including .angular-cli.json, protractor.conf.js, tsconfig.json, and tslint.json. This indicates a migration away from older Angular CLI versions (pre-Angular 8) and the Protractor end-to-end testing framework, likely as part of an upgrade to a newer Angular version and a shift to modern build and testing tooling.

src/angular/moviemanager · high confidence

The Angular Movie Manager application has removed several legacy configuration and entry-point files, including main.ts, polyfills.ts, styles.scss, test.ts, and associated TypeScript configuration files (tsconfig.app.json, tsconfig.spec.json, typings.d.ts). This cleanup eliminates older bootstrap logic, global Bootstrap CSS imports, and legacy polyfill/typing definitions, indicating a migration to a more modern Angular project structure or build tooling.

src/angular/moviemanager/src · high confidence

The application no longer uses the deprecated \WebSecurityConfigurerAdapter\-based security setup. This change removes the manual configuration of HTTP basic authentication, session management, and specific REST endpoint authorization rules, indicating a migration to a newer Spring Security model or externalized security policies.

src/main/java/ch/xxx/moviemanager · high confidence

The application's data access layer has been simplified by removing the custom \CustomRepository\ class and the legacy \Crud\*Repository\ interfaces that extended \CrudRepository\. These have been replaced with standard Spring Data JPA \JpaRepository\ interfaces for all entities (Actor, Cast, Genere, Movie, User). This change standardizes the repository implementation, leveraging Spring Data's built-in query derivation and pagination support instead of manual JPQL queries and entity manager usage.

src/main/java/ch/xxx/moviemanager/repository · high confidence

Initial test suite for Movie Manager backend; Removed legacy Spring Boot context loading test.

The Maven wrapper configuration has been updated to use Apache Maven 3.9.5 (upgraded from 3.5.2) and the Maven Wrapper JAR 3.2.0. This ensures that builds use a modern, stable version of the build tool and its wrapper infrastructure, improving compatibility and reliability across development environments.

.mvn · high confidence

The project has been upgraded to Spring Boot 4.1.0 and Java 25, replacing the previous Spring Boot 2.0 and Java 8 baseline. The frontend has been upgraded to Angular 22.0.1, ng-bootstrap 21.0.0-rc.0, and Bootstrap 5.3.2, replacing the legacy Angular 5 and Bootstrap 4 stack. The build structure has been modularized into separate backend and frontend Maven modules, with the frontend build now managed via the exec-maven-plugin to handle npm install and Angular CLI build steps.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 48 → 44 (-3.9)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 94 → 99 (+4.9)
• Architecture 92 → 73 (-19.0)
• Maturity 77 → 79 (+1.4)
• Readiness 60 → 43 (-16.9)
• Security 55 → 61 (+6.2)
• Domain Modelling 100 → 96 (-3.6)
• Accessibility 29 → 28 (-0.5)

• Change coupling: ActorService.java ↔ MovieService.java (backend/src/main/java/ch/xxx/moviemanager/usecase/service/ActorService.java)
• Change coupling: AuthenticationController.java ↔ UserDetailServiceBase.java (backend/src/main/java/ch/xxx/moviemanager/adapter/controller/AuthenticationController.java)
• Change coupling: actors.component.ts ↔ movies.component.ts (frontend/src/angular/src/app/actors/actors.component.ts)
• Change coupling: actors.service.ts ↔ movies.service.ts (frontend/src/angular/src/app/services/actors.service.ts)
• Change coupling: app.component.ts ↔ search.component.ts (frontend/src/angular/src/app/app.component.ts)
• Change coupling: movie-import.component.ts ↔ search.component.ts (frontend/src/angular/src/app/movie-import/movie-import.component.ts)
• Change coupling: movies.component.ts ↔ search.component.ts (frontend/src/angular/src/app/movies/movies.component.ts)
• Coverage not included — suite not readable by the collector
• Critical CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• Duplicated block (5 lines × 2) (backend/src/main/java/ch/xxx/moviemanager/usecase/service/ActorService.java)
• Duplicated block (6 lines × 2) (backend/src/main/java/ch/xxx/moviemanager/adapter/repository/ActorRepositoryBean.java)
• Duplicated block (6 lines × 2) (backend/src/main/java/ch/xxx/moviemanager/usecase/mapper/DefaultMapper.java)
• Duplicated block (6 lines × 2) (backend/src/main/java/ch/xxx/moviemanager/usecase/mapper/DefaultMapper.java)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• …and 47 more

• Change coupling: ActorController.java ↔ MovieController.java (backend/src/main/java/ch/xxx/moviemanager/adapter/controller/ActorController.java)
• Change coupling: ActorRepositoryBean.java ↔ ActorService.java (backend/src/main/java/ch/xxx/moviemanager/adapter/repository/ActorRepositoryBean.java)
• Change coupling: JpaActorRepository.java ↔ JpaMovieRepository.java (backend/src/main/java/ch/xxx/moviemanager/adapter/repository/JpaActorRepository.java)
• Change-coupling hub: MovieService.java → JpaActorRepository.java, JpaMovieRepository.java, MovieRepositoryBean.java, ActorService.java (backend/src/main/java/ch/xxx/moviemanager/usecase/service/MovieService.java)
• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no architecture or design documentation (README.md)
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (10 lines × 2) (backend/src/main/java/ch/xxx/moviemanager/usecase/service/ActorService.java)
• Duplicated block (5 lines × 2) (backend/src/main/java/ch/xxx/moviemanager/adapter/repository/ActorRepositoryBean.java)
• Duplicated block (5 lines × 2) (backend/src/main/java/ch/xxx/moviemanager/adapter/repository/ActorRepositoryBean.java)
• Duplicated block (5 lines × 2) (backend/src/main/java/ch/xxx/moviemanager/usecase/service/MovieService.java)
• Duplicated block (5 lines × 4) (backend/src/main/java/ch/xxx/moviemanager/adapter/controller/ActorController.java)
• Duplicated block (7 lines × 2) (backend/src/main/java/ch/xxx/moviemanager/usecase/mapper/DefaultMapper.java)
• Duplicated block (9 lines × 2) (backend/src/main/java/ch/xxx/moviemanager/usecase/mapper/DefaultMapper.java)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• High CVE: [GHSA redacted] (frontend/src/angular/package-lock.json)
• …and 71 more

• 16 commits — 16 feature/other, 0 fixes

• (repo) — 8 commits
• frontend/src — 7 commits
• helm/moviemanager — 1 commit

• change: Merge pull request #115 from Angular2Guy/dependabot/npm_and_yarn/frontend/src/angular/hono-4.12.31
• change: Merge pull request #118 from Angular2Guy/dependabot/npm_and_yarn/frontend/src/angular/tar-7.5.22
• change: Merge pull request #119 from Angular2Guy/dependabot/npm_and_yarn/frontend/src/angular/shell-quote-1.10.0
• change: Merge pull request #120 from Angular2Guy/dependabot/npm_and_yarn/frontend/src/angular/engine.io-6.6.9
• change: Merge pull request #122 from Angular2Guy/dependabot/npm_and_yarn/frontend/src/angular/socket.io-parser-4.2.7
• change: Merge pull request #123 from Angular2Guy/dependabot/npm_and_yarn/frontend/src/angular/ip-address-10.4.0
• change: Merge pull request #128 from Angular2Guy/dependabot/npm_and_yarn/frontend/src/angular/nanoid-3.3.18
• change: Merge remote-tracking branch 'origin/master'
• change: chore(deps): bump ip-address in /frontend/src/angular
• change: chore(deps-dev): bump nanoid in /frontend/src/angular
• change: feat: update Dockerfile
• change: feat: use signals
• change: feat: use signals
• change: feat: use signals
• change: feat: use signals
• change: feat: use signals

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Angular2Guy/MovieManager 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.