How adriantd3/shoppinglist works
Project type and purpose
• This is a full-stack “shopping list” application with:
• A Next.js / React Native-style frontend (“Dutylist”)
• A central Spring Boot monolith (ShoppingListApplication) handling auth, lists, items
• Two supporting Spring Boot microservices (Products & Users) generated via OpenAPI
• A relational database for persistence (db_structure.sql, db_data.sql)
• External identity provider (Firebase) used by the Users microservice
Break down the file structure into architectural components
• frontend/Dutylist → Mobile/Web app
• backend/ShoppingList → Monolithic REST API
• Modules: auth (JWT), lists (Shoplist, Item), products, utils
• backend/microservices/products → Products microservice (OpenAPI generator)
• backend/microservices/users → Users microservice (Firebase • Public/Private/Auth APIs)
• backend/database → SQL scripts for monolith’s database schema & seed data
• backend/openapi → JSON API contracts for Products & Users services
Extract key interactions from the code & README
• Frontend calls monolith for user workflows: login/register, create/view lists, add items
• Monolith:
• Manages user sessions (JWTFilter, SecurityConfig)
• CRUD on lists & items (ListController / ItemController → JPA Repositories)
• Basic product lookup (ProductController → ProductService)
• Monolith delegates to microservices for specialized domains:
• Products microservice (defined by openapi/productsapi.json)
• Users microservice (defined by openapi/usersapi.json)
• Microservices each persist to their own datastore (JPA Repositories)
• Users microservice calls Firebase for token verification (FirebaseConfig)
Components
a. Clients
– Web/Mobile UI (Dutylist Next.js + React-Native using Gluestack UI)
b. API layer
– ShoppingList Monolith (Spring Boot)
· Auth module (JWTFilter, AuthController → AuthService)
· Lists module (ListController, ItemController)
· Products module (basic product endpoints)
c. Microservices
– Products microservice (OpenApiGeneratorApplication, ProductsApiController)
– Users microservice (UsersApplication, AuthAPI / PublicAPI / PrivateAPI)
d. Datastores
– Relational DB for monolith (schema & data SQL)
– Separate DBs for each microservice
e. External services
– Firebase Authentication
Relationships & data flows
• UI → Monolith: HTTPS requests for all user interactions
• Monolith → Products microservice: HTTP calls per OpenAPI contract
• Monolith → Users microservice: HTTP calls for user/role queries (or direct DB? see code)
• Users microservice → Firebase: JWT token validation / user management
• Each service → own database: JPA writes/reads
Architectural patterns & principles
• Hybrid architecture: monolith + microservices
• Layered MVC in Spring Boot (controllers → services → repositories)
• Token-based security (JWT in monolith, Firebase in users service)
• API-first (OpenAPI for microservices)
• Domain separation: auth, lists, products, users