Adi Nišić

How I work

Built aroundfundamentals.

I lean on data shape, service boundaries, and delivery discipline, while keeping enough frontend range to ship the full product surface when needed.

A small example

Some endpoints on a .NET service had grown long Include and ThenInclude chains, pulling in more data than the response actually needed. Narrowing each query to just what the specific request used cut response times without changing the API.

Backend

  • NestJS / Node.js
  • .NET Core / C#
  • REST APIs
  • WebSockets
  • Modular monoliths and CQRS

Databases

PostgreSQL · MSSQL

Query tuning, schema design, service-side data modeling.

MongoDB · Redis

Caching, session data, lightweight document use cases.

Cloud & DevOps

  • AWS: EC2, S3, Lambda, RDS
  • Docker-based deployment
  • Linux server work and rollouts
  • GitHub Actions / CI

Frontend

Enough range to design, build, and refine usable interfaces while keeping the system model coherent.

AngularReactVueBlazorAstroTailwind

Mobile

  • Ionic
  • Flutter

Cross-platform features with shared backend thinking.

RedisGraphQLTypeScriptPostmanAzure