Overview
Architecture and proof of concept for programme registration, membership applications and scholarships.
Problem
Programme intake, membership and awards sit across systems. The first job is to decide what to build, what to buy and where the boundaries are.
My Role
Solution and vendor evaluation, build-versus-buy, system boundaries and a limited proof of concept.
What I Built
- Architecture and proof of concept for registration and application flows.
- Integration outline across programme, membership and award systems.
Architecture & decisions
Evaluation-led: boundaries first, then a limited proof of concept.
Technologies
- Spring
- Angular
- PostgreSQL
- Flyway
- AWS
- Lambda
- DynamoDB
- Bedrock
Outcome
Proof of concept and architectural recommendation.
Case boundary
The client and internal programme names are omitted.