Q26 — Clean Architecture — Solution Structure, Dependency Rule, Layer Responsibilities Level: Senior | Topic: Architecture The Core Principle — Dependency Rule In Clean Architecture, dependencies point inward only . The ...
1. Monolithic Architecture Extracted description: A single codebase and single deployable unit where all components are tightly coupled. Structure: UI / Web API → Business Logic + Data Access + Shared Components → Databa...
Here's a comprehensive breakdown of all 10 features, from junior through to principal engineer level. I'll build a visual architecture overview first, then walk through each. Now let's go deep on each feature, level by l...
This design assumes you want reliability, observability, security, compliance, scalability, and future flexibility. 1. Executive Architecture Summary A production AI-agent platform should not be just: User → LLM → Respon...
Monolithic — the starting point for most systems. A traditional monolith is a single process; a modular monolith enforces domain boundaries within it (great for teams not ready for microservices); vertical slice organise...
A medium-scale Azure blueprint for trusted Power BI semantic models, dynamic row-level security, staged deployment, and operational visibility.
A medium-scale Azure design for accepting documents, orchestrating durable processing, persisting results, and operating the workflow safely across the SDLC.
Design a small Firebase application around explicit Firestore access patterns, deny-by-default security rules, and transactional Cloud Functions, from local development through recovery.
A practical testing strategy for a medium-scale SaaS: use unit, integration, contract, and end-to-end tests at the right points in the SDLC, with Testcontainers for realistic dependencies.
A medium-scale AWS blueprint for deciding when event-driven functions simplify delivery, with concrete data, deployment, resilience, observability, and cost guidance.
A practical AWS EKS blueprint for running Loki, Grafana, Tempo, and Mimir with bounded retention, controlled cardinality, safe releases, and useful SLOs.
Design patterns are reusable solutions to common software design problems. They are not copy-paste code templates, but proven architectural ideas that help teams build systems that are easier to extend, test, maintain, a...
A practical, single-region Azure architecture for a small team building a secure .NET application with App Service, Azure SQL Database and Microsoft Entra ID.
A medium-scale AWS architecture for serving a static site and API through CloudFront, with practical guidance for data, delivery, observability, security, and recovery.
Q27 — CQRS with MediatR — Commands, Queries, Pipeline Behaviours Level: Senior | Topic: Architecture CQRS in a Nutshell Command Query Responsibility Segregation separates operations that change state (Commands) from oper...
A small-team architecture blueprint for a clinic booking app, from PostgreSQL conflict safety and App Service deployment to observability, recovery, and cost.
A medium-scale GCP SaaS architecture that combines Cloud Run, Cloud SQL, Pub/Sub, Memorystore, and Cloud Tasks across the software delivery lifecycle.
A practical, medium-scale SaaS architecture on Azure Container Apps, with Cosmos DB, Service Bus, Bicep, delivery practices, and operational guardrails.
A practical AWS architecture for a small internal admin tool, from Django and HTMX request handling through Celery jobs, safe releases, observability, and recovery.
SOLID is a set of five object-oriented design principles that help developers build software that is easier to maintain, extend, test, and refactor. The five principles are: S - Single Responsibility Principle O - Open/C...
A practical, example-driven guide to applying CQRS in real systems: when to use it, how to handle eventual consistency, the Outbox pattern, and operational considerations.
Part 1: The Foundations of Production .NET Services A practical guide for building, operating, and deploying reliable ASP.NET Core services on AWS. Audience: .NET developers moving from working APIs to production service...
A practical, detailed blueprint for building and operating a small-scale serverless web application on AWS using Lambda, API Gateway, DynamoDB, and CDK to optimize cost and simplicity.
Q7 — DI Service Lifetimes — Singleton, Scoped, Transient and the Captive Dependency Trap Level: Mid-Level | Topic: ASP.NET Core The Three Lifetimes Singleton: One instance per application. Created once, reused forever. U...
Event sourcing records every change as an immutable event. This article explains modeling choices, snapshots, upcasters, and safe external integrations.
Q3 — Explain the C# Type System: Records, Nullable Reference Types, and Pattern Matching Level: Mid-Level | Topic: C# Fundamentals Records (C# 9+) Records are compiler-synthesised types that provide value equality , immu...
Q11 — Eager, Lazy, and Explicit Loading — Differences and the N+1 Problem Level: Mid-Level | Topic: Entity Framework Core The Three Loading Strategies Eager Loading ( Include() ): Related data is loaded in the same query...
Thirteen AWS interview questions on disaster recovery, covering RTO and RPO, regional failover, data replication, recovery testing, and operational readiness.