Architecture

1. Overview

This module contains architecture documentation for the Event and Membership Administration System, including integration patterns, system design, and architectural decisions.

2. Document Categories

Category Description

Integration Architecture

Patterns for integrating with external systems and platforms

System Design

Core system architecture and component interactions

Data Architecture

Data models, flows, and persistence patterns

3. Current Documentation

3.1. Service Patterns

  • Microservice Pattern — The shared deployment, build, CI/CD and observability baseline every EMS service follows. Read this first when bootstrapping anything new.

  • Portal Pattern — Gateway + Angular SPA topology, OIDC client, session-held JWT, server-side tenant resolution, same-origin browser scope.

  • MCP Pattern — OAuth resource server exposing admin-service via Model Context Protocol to LLM-driven clients (Cowork).

  • Java Library Pattern — Maven JAR artefacts published to GitHub Packages (parent-pom, event-database, wordpress-database, spreadsheet-importer). Re-uses the CI/CD half of the microservice baseline; drops Jib / Helm / ArgoCD.

3.2. Portal Concerns

  • Gateway + Angular SPA — The canonical topology for EMS frontends: Spring Boot gateway + Angular SPA, session-held JWT, server-side tenant resolution, same-origin browser scope

  • OIDC ⇄ admin-service Token Exchange — Trust model, claim mapping, JIT provisioning, and the runtime-tenant-switch design gap

  • Session-Held JWT & JSESSIONID — Where the JWT lives, the relay filter, OIDC refresh state machine, logout, CSRF posture

  • API-Key Injection at the Gateway — Why portals authenticate themselves with X-API-KEY, gateway-side injection mechanics, rotation procedure

  • SPA Cache & CDN Strategy — Per-path-class cache-control rules, hashed assets immutable, index.html no-cache, Cloudflare CDN-Cache-Control

  • OpenAPI Contract Flow — admin-service as spec source of truth, CI extraction, in-portal TypeScript client generation, dayjs transformer

  • Hazelcast Configuration — Embedded member topology, four-tier discovery, session replication, EMS-custom security-dimension caches

  • SpringApplication Bootstrap — Shared main-class convention, profile validation, startup banner, profile inventory

  • Dev-Mode UI Awareness — webpack DefinePlugin flag, gated behaviours, proposed shared dev-banner component

  • JHipster — Keep & Drop — What we retain from JHipster conventions vs what we leave behind as we move to greenfield portals

3.3. Integration

3.4. File Import

  • File Import - XLSX and CSV spreadsheet import with dictionary-based column mapping

  • Async Import - Asynchronous import processing with interactive mapping resolution

3.5. Domain

4. Related Documentation

5. Architecture Decision Records

Durable records of significant decisions — what was decided, why, and what alternatives were rejected. ADRs are read whenever someone asks "why did you do it this way?" or "why not the other way?".