Technology Decisions Based on Product Requirements

Server applications that hold the business rules, enforce authorization and expose predictable interfaces to every client.

• .NET 8

  Primary runtime for enterprise backends, desktop applications and long-lived business systems.

• ASP.NET Core

  Web APIs built with Clean Architecture, CQRS through MediatR and centralized exception handling.

• C#

  The primary language for domain models, application services and business rule implementation.

• Entity Framework Core

  Code-first data access with explicit configuration, constraints, indexes and versioned migrations.

• Laravel

  Used for PHP-hosted product work where the deployment environment or team continuity favours it.

• Node.js

  Server runtime for Next.js applications, build tooling and lightweight service endpoints.

• REST APIs

  Consistent resource design, standard status codes, pagination and a single response envelope.

Interfaces built for performance, accessibility and bilingual use, with layout that works in both text directions.

• Next.js

  App Router with server components as the default, static generation where content allows it.

• React

  Component model for interactive interfaces, product dashboards and internal portals.

• TypeScript

  Strict typing across frontend code, shared validation schemas and content structures.

• Tailwind CSS

  Utility styling with logical properties so one stylesheet serves both left-to-right and right-to-left.

• shadcn/ui

  Accessible component patterns owned in the codebase rather than hidden behind a dependency.

• TanStack Query

  Server state, caching and background refresh in data-heavy product interfaces.

• Zod

  Shared validation schemas used by both the browser form and the server route.

Applications for field teams and on-site operations, including environments where connectivity cannot be assumed.

• React Native

  Cross-platform mobile applications from a single TypeScript codebase.

• Expo

  Build, distribution and update tooling for React Native product releases.

• WPF

  Windows desktop clients for offline-first trading and warehouse operations.

• WinForms

  Used for straightforward desktop business applications where a simple, fast interface is the priority.

• SQLite

  Local storage for offline-capable mobile and desktop applications with explicit schema migrations.

Relational databases designed with constraints and indexes, because reporting is only as trustworthy as the schema beneath it.

• SQL Server

  Default relational database for ERP and desktop business systems, including on-premise deployments.

• PostgreSQL

  Preferred relational database for cloud-hosted product and SaaS workloads.

• MySQL

  Used where the hosting environment or an existing application already standardizes on it.

• Redis

  Caching, queues and rate limiting when load or background processing justifies it.

• Database design

  Explicit keys, foreign keys, unique constraints, indexes, audit columns and soft deletion by default.

Reproducible environments, controlled releases and the operational plumbing that keeps a system supportable.

• Docker

  Consistent development, staging and production environments through container definitions.

• Azure

  Cloud hosting option for .NET workloads, managed databases and application services.

• GitHub Actions

  Automated build, test and deployment pipelines with environment-scoped secrets.

• Git

  Version control with reviewed changes and semantic version tags for every release.

• Nginx

  Reverse proxy, TLS termination and static delivery for self-hosted deployments.

• Serilog

  Structured logging with correlation identifiers and no sensitive payloads in log output.

Applied to specific operational steps with defined inputs, defined outputs and a human checkpoint where judgement is required.

• OpenAI APIs

  Used for classification, extraction and summarization tasks where the output is reviewed before it is acted on.

• n8n

  Workflow orchestration for routing, scheduled jobs and integrations between business tools.

• Webhooks & event flows

  Event-driven handoffs between systems with defined retry and failure behaviour.

• Background workers

  Idempotent scheduled and queued jobs for notifications, reports and data maintenance.

• Human-in-the-loop review

  Approval and correction steps designed into automated workflows, with every correction recorded.