PORTFOLIO / PROJECTS / ENTERPRISE-OPERATIONS-PLATFORM02 / 02
All projects

Enterprise Operations Platform.

An enterprise operations management platform built with ASP.NET Core Web API and React (Next.js, TypeScript), designed for modular workflows and long-term iteration.

Highlights

  1. Multi-module system: meetings, tasks, decisions, workflow automation, documents, notifications, analytics
  2. Clean Architecture + CQRS with MediatR and FluentValidation
  3. Secure auth with JWT, RBAC, and multi-tenant approach
  4. Scalable infra and realtime: PostgreSQL, Redis, SignalR, Hangfire, Docker

PROBLEM

Organizations often run meetings, decisions, tasks and documents in separate tools. Action items from a meeting get lost on the way to the task tracker, decisions lack an approval trail, and nobody has a single view of operations. A platform that brings these together has to serve many organizations at once (multi-tenant), keep each tenant's data isolated, enforce fine-grained permissions and leave an audit trail, without the codebase falling apart as modules multiply.

SOLUTION

I built EOP on Clean Architecture with four layers (Api, Application, Domain and Infrastructure) plus shared building blocks. Every use case is a CQRS command or query dispatched through MediatR, with pipeline behaviors handling logging, validation (FluentValidation) and error handling in one place. Multi-tenancy is enforced by tenant-context middleware and EF Core query filters; permission-based authorization lives in the API and is mirrored in the Next.js/React UI. PostgreSQL stores the data, Redis handles caching, SignalR delivers real-time notifications, Hangfire runs background jobs, and Microsoft Graph connects Teams, Outlook, SharePoint and OneDrive.

Results

  1. 11 modules (meetings, decisions, tasks, documents, workflows, notifications, analytics, search, Microsoft 365, background jobs and administration) on one API with shared identity and permissions
  2. Cross-cutting concerns (logging, validation, error handling) handled once in the MediatR pipeline instead of in every endpoint
  3. Tenant data isolated by middleware and query filters; permissions enforced in the API and reflected in the UI
  4. Covered by xUnit and Playwright tests, packaged with Docker Compose and built with GitHub Actions
NEXT →FitLog