HomeServicesProjectsAboutContact

Projects

Projects that demonstrate how I approach backend engineering.

These projects are currently in development. I document completed functionality, technical decisions, and upcoming work separately.

In development

Identity Provider

An authentication and authorization service for applications that need centralized identity management.

Problem

Applications often duplicate login, token handling, and role checks across services. A dedicated identity service helps keep those concerns consistent.

Currently implemented

  • Authentication model and token strategy
  • Role-based access control design
  • Tenant-aware service structure

Technical approach

  • Keep identity concerns separate from product services so authentication and authorization rules stay consistent.
  • Use Spring Security and JWT-based flows to handle login, token issuance, and protected APIs.
  • Model tenants, roles, and clients explicitly so the system can grow without spreading auth logic across multiple applications.

Technology stack

JavaSpring BootSpring SecurityJWTPostgreSQLRedisDocker

Next steps

  • OAuth2 and OpenID Connect improvements
  • Multi-tenant support expansion
  • Identity federation
  • Admin console
  • Audit logging
  • Deployment hardening

System outline

Identity Provider
API layer
Processing logic
Data layer
In development

Bliq Messaging

A messaging-focused application for reliable communication workflows, delivery tracking, and user-facing message management.

Problem

Messaging workflows need clear conversation state, delivery reliability, and a clean interface for users without spreading message logic across the product.

Currently implemented

  • Messaging workflow structure
  • Conversation and delivery-state planning
  • Frontend interface foundations

Technical approach

  • Model conversations, participants, and message state explicitly so the application remains maintainable as features grow.
  • Keep communication logic separated from the UI so delivery handling and interface changes can evolve independently.
  • Design the interface around fast scanning, message history, and practical day-to-day communication flows.

Technology stack

JavaSpring BootReactNext.jsTypeScriptPostgreSQLDocker

Next steps

  • Real-time message updates
  • Delivery status improvements
  • Search and filtering
  • User and conversation management
  • Deployment hardening

System outline

Bliq Messaging
API layer
Processing logic
Data layer
In development

Techflue

A technology-focused web platform built around structured content, clean presentation, and maintainable product pages.

Problem

Technical businesses need a website that communicates services clearly, supports updates, and stays easy to maintain as offerings change.

Currently implemented

  • Content-first page structure
  • Responsive frontend layout
  • Reusable section and data patterns

Technical approach

  • Use structured content data so project and service information can be updated without touching every page.
  • Build reusable frontend sections that keep the site consistent across home, services, and project views.
  • Keep the design direct and readable so visitors can understand the offering quickly.

Technology stack

ReactNext.jsTypeScriptTailwind CSSVercel

Next steps

  • Case study expansion
  • CMS or content workflow
  • SEO refinements
  • Contact flow improvements
  • Performance review

System outline

Techflue
API layer
Processing logic
Data layer

Need similar backend or product engineering support?

I can help scope the work, implement the right pieces, and keep the delivery path practical.

Discuss a Project