How cuevaserik-dev/micro-stripe works
This is a minimal Spring Boot subscription-domain application: its visible runtime entry point starts the Spring application, while the model defines plans, users, subscription records, and subscription status. The excerpts show JPA entity mappings and their associations, but no API, service, repository, or user-to-subscription workflow. The graph therefore captures only startup and model relationships; database configuration and operational behavior are not established by the available source.
Main entry points: Subscription.java Subscription · Plan.java Plan · User.java User · DemoApplication.java Spring Boot app
Components 6
Application runtime
- Spring Boot app
src/main/java/com/israel/subscription/DemoApplication.java
Subscription domain
- Subscription
src/main/java/com/israel/subscription/model/Subscription.java - Plan
src/main/java/com/israel/subscription/model/Plan.java - User
src/main/java/com/israel/subscription/model/User.java - Subscription status
src/main/java/com/israel/subscription/model/StatusSubscripcion.java
Other components
- JVM
Connections 6
- JVM → Spring Boot app: starts
src/main/java/com/israel/subscription/DemoApplication.java - Subscription → Plan: references
src/main/java/com/israel/subscription/model/Subscription.java - Subscription → User: references
src/main/java/com/israel/subscription/model/Subscription.java - Subscription → Subscription status: stores status
src/main/java/com/israel/subscription/model/Subscription.java - Plan → Subscription: maps collection
src/main/java/com/israel/subscription/model/Plan.java - User → Subscription: maps collection
src/main/java/com/israel/subscription/model/User.java