Master technical and career interviews with structured answers—short definition, real examples, pitfalls, and how to answer in 60–90 seconds.
Short answer: Caching expensive requests where model binding is unnecessary. Real-world example (ShopNest) A ShopNest ValidateModelAttribute runs before actions and returns 400 if ModelState is invalid—same rule for ever…
Short answer: compression In-memory caching stores data on server memory for fast retrieval. Distributed caching uses external stores (Redis, SQL) for multiple servers. Response compression reduces payload size using gzi…
Short answer: Use Redis or SQL Server for distributed cache/session in multi-server environments. Helps maintain session state without sticky sessions. Real-world example (ShopNest) ShopNest registers AppDbContext as Sco…
Short answer: Apply Dependency Inversion Principle by coding against abstractions (interfaces), not implementations. Follow SOLID principles: Single Responsibility: Each class has one reason to change. Open/Closed: Class…
ASP.NET Core ASP.NET Core Tutorial · ASP.NET Core
Short answer: Caching expensive requests where model binding is unnecessary.
A ShopNest ValidateModelAttribute runs before actions and returns 400 if ModelState is invalid—same rule for every controller.
ASP.NET Core ASP.NET Core Tutorial · ASP.NET Core
Short answer: compression In-memory caching stores data on server memory for fast retrieval. Distributed caching uses external stores (Redis, SQL) for multiple servers. Response compression reduces payload size using gzip, Brotli middleware.
ShopNest registers AppDbContext as Scoped and IMemoryCache as Singleton. Putting DbContext in a Singleton causes threading bugs.
ASP.NET Core ASP.NET Core Tutorial · ASP.NET Core
Short answer: Use Redis or SQL Server for distributed cache/session in multi-server environments. Helps maintain session state without sticky sessions.
ShopNest registers AppDbContext as Scoped and IMemoryCache as Singleton. Putting DbContext in a Singleton causes threading bugs.
ASP.NET Core ASP.NET Core Tutorial · ASP.NET Core
Short answer: Apply Dependency Inversion Principle by coding against abstractions (interfaces), not implementations. Follow SOLID principles: Single Responsibility: Each class has one reason to change. Open/Closed: Classes open for extension, closed for modification. Liskov Substitution: Subtypes can replace base types. Interface Segregation: Use multiple specific interfaces. Dependency Inversion: Depend on abstractions.
A ShopNest checkout request flows through middleware, hits a minimal API or controller, uses scoped services, and returns ProblemDetails on errors.
Install Toolliyo like an app Free
Home-screen access to tutorials, coding practice & career tools — no app store needed.
On iPhone/iPad: tap Share then Add to Home Screen.