Skip to content
Taher Samman

Case study · Personal project

Alfa uShare Business Manager

A full-stack tool I built end to end in 2026 to manage shared mobile-data lines: an Angular dashboard, a Spring Boot API with JWT login, and a Node.js service that keeps balances and expiry dates in sync.

Role
Designed and built end to end by me
Project period
March to August 2026
Type
Personal project, a private business tool
Stack
Angular, Spring Boot, Node.js, PostgreSQL
  • 3

    services working together: dashboard, API and sync service

  • 5

    dashboard screens: lines, bundles, debtors, expenses and targets

  • Daily

    automatic sync, plus a button to run it on demand

  • Live

    sync progress streamed to the dashboard over a WebSocket

The context

One place for every line.

The system keeps each line's balance, expiry date and shared users in one place, refreshes them automatically, and keeps the money side (debtors, payments and expenses) next to them. It is a private tool, so no real numbers or customer data appear here.

  • Angular dashboard
  • Spring Boot API
  • Node.js sync service
  • PostgreSQL database

How it is built

Three services, each with one job.

I designed the split so the screen, the rules and the browser work can each change on their own:

  • 01

    Dashboard (Angular 19)

    • Lines with live sync progress
    • Bundle expiry dates
    • Debtors, invoices and payments
    • Expenses and a targets chart
    • Light and dark themes
  • 02

    API (Spring Boot)

    • REST endpoints for lines, clients, debtors and expenses
    • JPA entities on PostgreSQL
    • WebSocket stream of sync progress
    • Daily scheduler with an email notice
  • 03

    Sync service (Node.js)

    • Headless browser reads each line in turn
    • Replies at once, then reports progress by job
    • Sends each result to the API as it finishes
    • Keeps a last-sync snapshot on disk

Security

Login and sessions.

  • JWT login

    Sign-in issues a JWT carried in a cookie. Every API route needs it, apart from login and the sync endpoints.

  • A logout that works

    Signed-out tokens go into a database blocklist, which is cleaned of expired entries every five minutes.

  • Hashed passwords

    Passwords are stored with BCrypt, and the cookie's secure flag is set by configuration.

  • Clean errors

    Unauthorized and forbidden responses return plain JSON, and allowed origins come from configuration.

Delivery

Live by design.

Delivery

A long job should never hold a request open. The sync service answers straight away with a job ID, then reports each finished line to the API, which records the sync time and pushes a "synced" event to the dashboard.

Shipped as containers and a static site

The sync service runs in a Docker container on Render, the API ships with its own Dockerfile, and the dashboard is hosted on Firebase.

What I took from it

  • 01

    A long job needs a job ID and live progress, not a long-held request.

  • 02

    Give each concern its own service, so the screen, the rules and the browser work change independently.

Stack

  • Angular
  • TypeScript
  • Tailwind CSS
  • Spring Boot
  • Java
  • Spring Security
  • JWT
  • PostgreSQL
  • WebSocket
  • Node.js
  • Express
  • Playwright
  • Docker
  • Firebase

Want full-stack work like this on your team?

© 2026 Taher Samman