SaaS, fintech, enterprise workflows, distributed systems and applied AI.
Live Technical Proof
This Portfolio Is Also a Product Engineering Prototype
The site demonstrates the same engineering judgement I bring to SaaS and AI products: clean backend structure, database-driven content, SEO control, caching, analytics and a simple production model.
Visitor Request
Spring MVC
SeoService
Services
Repositories
SQLite
Thymeleaf Response
Profile, projects, experience, skills, services, SEO and translations are database-backed.
Child collections are batch-loaded and translations are request-scoped.
What It Proves
Architecture Choices You Can Inspect
A serious portfolio should not only say “I build products”. It should show product thinking, implementation discipline and operational restraint in the product itself.
Database-driven portfolio engine
The site is no longer hardcoded content. It uses SQLite-backed models for profile, projects, services, skills, experience, SEO and translation state.
- Single active profile today, evolvable toward multi-profile later
- Repository/service/view-model separation
- Hidden records and sort order respected in public views
SEO as a first-class service
Every public page receives a structured SEO model for titles, descriptions, canonical URLs, Open Graph, Twitter metadata and JSON-LD.
- Manual Thymeleaf SEO rendering
- DB-backed route metadata
- Noindex handling for private and error pages
Performance-minded content loading
The public pages use Spring caching and batch repository methods so repeated traffic does not repeatedly rebuild the same content graph.
- Caffeine public-content caches
- Bulk project technology, experience bullet and skill queries
- Request-level translation cache
Translation-ready architecture
English remains the source of truth while generic translation tables can support profile, project, service, SEO and content-block fields later.
- Stable source hashes
- Safe English fallback
- Scheduled job disabled by default
Stack and Boundaries
Simple Where It Should Be, Structured Where It Matters
The prototype keeps the deployment small while giving the content, SEO and translation systems clear boundaries.
Application
One deployable Java 17 Spring Boot JAR with Spring MVC and Thymeleaf.
Persistence
SQLite is used for analytics and portfolio content without adding external infrastructure.
Public Content
Portfolio content is read through services and rendered through stable view models.
Operations
The app keeps the existing production model: static assets, security, analytics and single-JAR deployment.
Engineering Judgement
Principles Behind the Build
Loose coupling
Controllers compose page models while services own business assembly and repositories own SQL.
Simple deployment
The prototype stays one Spring Boot app with SQLite and avoids extra infrastructure too early.
Search-ready rendering
Important SEO tags are server-rendered in Thymeleaf instead of depending on client-side hydration.
Future admin path
The data model already separates editable content from rendering, so admin screens can evolve safely.