CSharp Developer

Understand how read-heavy and write-heavy workloads affect System Design. This practical guide explains read and write traffic, caching, read replicas, database performance, transactions, concurrency, and how a simple read/write traffic calculation can influence architecture decisions in .NET applications.

Ajay NarkhedkarSep 274,1591,000

Learn how to estimate application traffic before designing a scalable system. This practical guide explains the difference between users, requests, concurrent users, average traffic, and peak traffic, with an e-commerce example and a simple C# calculation for estimating requests per second.

Ajay NarkhedkarSep 274,5521,000

Learn how to identify users, roles, permissions, and use cases before designing APIs and architecture. This practical guide uses an e-commerce system to show how business requirements can be mapped from users and roles to use cases, features, and ASP.NET Core APIs.

Ajay NarkhedkarSep 274,6231,000

Learn how real-world constraints such as budget, team size, existing systems, technology limitations, and delivery timelines influence System Design. This practical guide explains how .NET developers can balance business requirements with real-world limitations to create simpler, maintainable, and realistic software architectures.

Ajay NarkhedkarSep 263,2821,000

Understand the difference between Functional and Non-Functional Requirements using a practical Order Management System example. Learn how the same feature can be viewed from two perspectives and how performance, security, availability, and scalability requirements influence ASP.NET Core system design.

Ajay NarkhedkarSep 264,4591,000

Understand Non-Functional Requirements from a practical .NET developer's perspective. Learn how performance, availability, security, and scalability requirements influence ASP.NET Core APIs, database design, architecture, and real-world System Design decisions.

Ajay NarkhedkarSep 222,9991,000

Learn what Functional Requirements really mean and how .NET developers can convert business requirements into users, actions, features, business operations, and APIs. This practical guide uses an Order Management System to explain how requirements become the foundation of effective System Design.

Ajay NarkhedkarSep 222,7021,000

Learn how .NET developers can understand and break down software requirements before writing code. This practical guide explains how to identify the problem, users, system actions, use cases, business rules, data, and functional and non-functional requirements using a real-world Order Management System example.

Ajay NarkhedkarSep 215,0141,000