Commit Graph

29 Commits

Author SHA1 Message Date
stefan a3a3a5f87c fix port conflict and KeycloakIntegrationTest.kt 2025-09-06 11:27:37 +02:00
stefan 4af276e67a fix tests 2025-09-05 13:52:45 +02:00
stefan f160dd2988 fix tests 2025-09-05 11:33:29 +02:00
stefan 1eb00ad15d update auth-module ping-service consul 2025-09-04 21:01:49 +02:00
stefan 6f157460e1 optimierungen Trace-Bullet 2025-09-04 16:09:28 +02:00
stefan 6675e2de94 optimierungen gateway-Modul 2025-09-04 13:54:30 +02:00
stefan 63a1b97db7 optimierungen auth-Modul und cache-Modul 2025-09-03 15:19:11 +02:00
stefan 2c2dcd381c fixing(gradle) 2025-08-27 00:30:53 +02:00
stefan 8fd09a4aa1 fixing(gradle) 2025-08-25 21:15:25 +02:00
stefan 89ef9698af fixing(gradle) 2025-08-24 21:31:31 +02:00
stefan 9c21154199 upgrade(docker) 2025-08-16 15:47:57 +02:00
stefan 846918cf69 fixing(infra-messaging) 2025-08-15 01:17:24 +02:00
stefan 5e8cd6f79d refactoring(Gateway)
TODO-Roadmap.md
Micrometer Metrics Integration for Observability in Gateway
2025-08-14 14:41:03 +02:00
stefan 47a450ccb1 refactoring(Gateway Health Indicator implementieren)
TODO-Roadmap.md
1.2 Health Check Verbesserungen
2025-08-14 13:58:55 +02:00
stefan eeda3b7ac2 refactoring(Gateway Health Indicator implementieren)
TODO-Roadmap.md
1.2 Health Check Verbesserungen
2025-08-14 13:54:06 +02:00
stefan d0232c23a0 fixing(gateway) 2025-08-14 00:35:51 +02:00
stefan b67d75543e fixing(gateway) 2025-08-13 21:46:23 +02:00
stefan 562eb07be1 fixing(Gateway) 2025-08-13 14:18:59 +02:00
stefan a50b1b3822 feat(Tracer Bullet) 2025-08-11 23:47:05 +02:00
stefan 582678e226 refactor(infra-monitoring)
refactor(infra-gateway)
2025-08-11 14:32:01 +02:00
stefan 1db41a5c62 refactor(core): Stabilize and Refactor Shared Kernel
This commit introduces a comprehensive refactoring and stabilization of the core module, establishing a robust and well-tested foundation (Shared Kernel) for all other services.

The module has been thoroughly analyzed, cleaned up, and equipped with a professional-grade test suite.

Architectural Refinements:
- Slimmed down `core-domain` to be a true, minimal Shared Kernel by removing all domain-specific enums (`PferdeGeschlechtE`, `SparteE`, etc.). This enforces loose coupling between feature modules.
- The only remaining enum is `DatenQuelleE`, which is a cross-cutting concern.

Code Refactoring & Improvements:
- Refactored the configuration loading by introducing a `ConfigLoader` class. This decouples the `AppConfig` data classes from the loading mechanism, significantly improving the testability of components that rely on configuration.
- Unified the previously duplicated `ValidationResult` and `ValidationError` classes into a single, serializable source of truth, ensuring consistent error reporting across all APIs.

Testing Enhancements:
- Introduced a comprehensive test suite for the core module, bringing it to a production-ready quality standard.
- Implemented the "gold standard" for database testing by replacing the previous H2 approach with **Testcontainers**. The `DatabaseFactory` is now tested against a real, ephemeral PostgreSQL container, guaranteeing 100% production parity.
- Added robust unit and integration tests for critical components, including the new `ConfigLoader`, all custom `Serializers`, and the `ApiResponse` logic.
- Fixed all compilation and runtime errors in the test suite, resulting in a successful `./gradlew clean build`.
2025-08-05 18:25:21 +02:00
stefan a9a43a7acf fixing Gradle 2025-08-01 11:31:29 +02:00
stefan df5919fac8 feat(build): Refactor infrastructure modules and establish single source of truth
This commit introduces a major refactoring of the build system and the core infrastructure modules. The primary goal is to establish a strict "Single Source of Truth" for all dependencies using Gradle Version Catalogs and to create a clean, maintainable, and scalable foundation for all current and future services.

### 1. Centralized Dependency Management (`libs.versions.toml`)

- **Established Single Source of Truth:** All dependency versions are now exclusively managed in `gradle/libs.versions.toml`. Hardcoded versions have been removed from all build scripts.
- **Introduced Gradle Bundles:** To simplify module dependencies, several bundles have been created (e.g., `testing-jvm`, `redis-cache`, `spring-cloud-gateway`, `monitoring-client`). This drastically reduces boilerplate in the `build.gradle.kts` files and improves readability.
- **Cleaned up Aliases:** All library and plugin aliases have been standardized for consistency.

### 2. Infrastructure Module Refactoring

All infrastructure modules (`core`, `platform`, `auth`, `cache`, `event-store`, `messaging`, `monitoring`, `gateway`) have been refactored to align with the new dependency management strategy.

- **Simplified Build Scripts:** The `build.gradle.kts` for each module now uses the new bundles and aliases, making them significantly cleaner and easier to understand.
- **Consistent Structure:** The architecture of each module now clearly follows the Port-Adapter pattern where applicable (e.g., `cache-api`/`redis-cache`).
- **Standardized `platform-bom`:** The project's own Bill of Materials (`platform-bom`) now also includes the Spring Cloud BOM, ensuring version consistency for all Spring-related dependencies.

### 3. Added Infrastructure Documentation

To improve onboarding and architectural understanding, a dedicated `README-*.md` file has been created for each refactored infrastructure module:
- `README-CORE.md`
- `README-PLATFORM.md`
- `README-INFRA-AUTH.md`
- `README-INFRA-CACHE.md`
- `README-INFRA-EVENT-STORE.md`
- `README-INFRA-MESSAGING.md`
- `README-INFRA-MONITORING.md`
- `README-INFRA-GATEWAY.md`

These documents explain the purpose, architecture, and usage of each component within the system. This lays the groundwork for our "Tracer Bullet" development approach.
2025-07-31 14:09:22 +02:00
stefan 81cb4582d6 fixing gradle build 2025-07-31 00:02:12 +02:00
stefan ea75bbdb24 fixing gradle build 2025-07-30 00:01:22 +02:00
stefan 7e0b56a247 einige Ergänzungen 2025-07-25 23:16:16 +02:00
stefan a4c7d53aa3 refactor: Migrate from monolithic to modular architecture
### **Service-Implementation**
- [ ] **Tag 1**: Members-Service REST-API implementieren
- [ ] **Tag 2**: Database-Migrations und Repository-Layer
- [ ] **Tag 3**: Event-Publishing nach Kafka aktivieren
- [ ] **Tag 4**: Horses-Service analog implementieren
- [ ] **Tag 5**: Integration-Tests für beide Services
- [ ] **Tag 6-7**: Events-Service und Masterdata-Service
2025-07-24 17:18:22 +02:00
stefan e7b18da45d refactor: Migrate from monolithic to modular architecture
1. **Docker-Compose für Entwicklung optimieren**
2. **Umgebungsvariablen für lokale Entwicklung**
3. **Service-Abhängigkeiten**
4. **Docker-Compose für Produktion**
5. **Dokumentation**
2025-07-24 14:20:48 +02:00
stefan a256622f37 refactor: Migrate from monolithic to modular architecture
- Restructure project into domain-specific modules (core, masterdata, members, horses, events, infrastructure)
- Create shared client components in common-ui module
- Implement CI/CD workflows with GitHub Actions
- Consolidate documentation in docs directory
- Remove deprecated modules and documentation files
- Add cleanup and migration scripts for transition
- Update README with new project structure and setup instructions
2025-07-22 18:44:18 +02:00