What problem does it solve?
PayU's backend architecture is highly complex and demands disciplined design to ensure modularity, scalability, and resilience across multiple services. This skill provides a blueprint for building core banking systems using Hexagonal Architecture, domain-driven design, and resilient patterns. It offers governance and best-practice guidance to unify Spring Boot 3.4 and Quarkus-native workloads under a coherent architectural standard.
Core Features & Use Cases
- Hexagonal Architecture blueprint: Domain logic remains free of framework dependencies; ports and adapters connect to infrastructure.
- DDD & Architecture Governance: Enforce clean boundaries with ArchUnit rules and domain events.
- Resilience, Transactions & Caching: Guidance on transactional boundaries, outbox patterns, idempotency, and layered caching strategies.
- Cross-cutting guidance: Spring Boot 3.4 patterns, Quarkus native considerations, and performance-oriented Java patterns for multi-service environments.
Quick Start
Define a new core banking service blueprint and outline the Transfer use case, including domain entities, ports, adapters, and transaction boundaries.